HP3000-L Archives

October 1996, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jon Cohen <[log in to unmask]>
Reply To:
Jon Cohen <[log in to unmask]>
Date:
Thu, 10 Oct 1996 08:59:08 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
[log in to unmask] wrote: ...

... a very good thesis about our release & OS V.UU.FF numbering
conventions.

Speaking personally,

   o  The Release V.UU.FF should be of interest to customers.
      Basically,
         1)  Releases should sort appropriately.  An earlier
             release would be sorted before a later release.
         2)  You should be able to get an indication from the
             V.UU.FF about which release is which.  For example,
             C.55.03 would be 5.5 Express 3 (or 5.5 Powerpatch 3).

   o  OS V.UU.FFs are internal names.  Other than the fact that
      the V.UU.FFs would sort, these V.UU.FFs should have no
      meaning to customers.  We basically use the OS V.UU.FFs
      to isolate the presence of a bug and/or its fix.

And (again speaking personally), I don't understand why customers
are interested in the "meanings" of the V.UU.FFs.  There really
aren't any hidden "meanings" -- we just use the V.UU.FFs to track
the various different versions of our software, so that we can
support you better.  Can someone elighten me?

--
Jon Cohen
[log in to unmask]
Hewlett Packard -- Commercial Systems Division

(The opinions expressed here gotta be mine, 'cause no
one else will own up to 'em.)

ATOM RSS1 RSS2