HP 3000 Manuals

COMMUNICATOR 3000/XL Release 1.0 (A.02.00)

Chapter 2  RELEASE NOMENCLATURE 

Naming Convention and VUF Nomenclature For Commercial Systems XL Releases 

by Carl Cicero--Computer Systems Division 

This article outlines the naming convention and VUF nomenclature for all
Commercial Systems XL Releases.  Its purpose is to characterize the
various releases and define the current strategy being used to identify
them.

NAMING CONVENTION 

The naming convention for Commercial Systems XL Releases consist of two
sections.  One convention covers the names used to identify the groups of
Commercial Systems XL Releases.  These groups provide a set of core
functionality.  The other convention covers the names used to identify
the TYPE of releases within these groups.

Release Name 

The release name identifies the group of individual releases that provide
a set of planned core functionality.  For example, Release 1.0 is the
name given to the releases with the first set of core functionality.
Release 1.1 is the name given to the releases with the second set of core
functionality.  And so on.


NOTE  An important point to make at this time is that the release name is
      NOT derived from the release VUF or vise versa.  For example, the
      "1.0" in Release 1.0 did NOT come from the VUF of A.01.00.


Types of Releases 

The second naming convention covers the names used to identify the TYPE
of release.  This is different from the names used to identify the
release.  For example, "1.0" is the release name, but that release has
several types.

There are several types of releases which need to be represented by the
naming convention.  These types are differentiated by the "level of
change" being made to the release.  The level of change is also used to
determine how the release VUF is modified.  The types of releases are:

                NL Build
                Patch Build
                Production Release
                Core Software Release
                Major Release

NL BUILD 

A Field Replacement Unit (FRU). A reactive solution to solving time
critical customer problems that cannot be resolved in another more
efficient manner.  NL Builds are shipped to specific customers on an as
needed basis.  Level Of Change:  A FRU in the NL.

PATCH BUILD 

A Defect Repair Build.  A complete build of the SLT, FOS and SUBSYS
destined for distribution to all customers.  No enhancements or new
products are included in this type of release.  A Patch Build integrates
"general release" patches and solutions for critical problems.  Level Of
Change:  A set of FRUs.

PRODUCTION RELEASE 

A release vehicle for new software and fixes/enhancements to existing
products.  Also provides support for new software, plug compatible
peripherals and co-development.  It is built on top of the latest Patch
Build.  Level Of Change:  Minimum or no NL changes.  Additional OS
changes are held to a minimum.

CORE SOFTWARE RELEASE 

Major changes to the OS, Turbo/XL or low level datacomm.  It maintains a
functional level no less than the latest or concurrent Production
Release.  Level Of Change:  Has major changes to integrate SR fixes and
enhancements.

MAJOR RELEASE 

A complete rewrite of a major portion of the OS. Level Of Change:  Major
rewrite.

VUF NOMENCLATURE 

The VUF nomenclature establishes how the release VUF is modified.  It is
important to remember that the Commercial Systems XL Release VUF has been
decoupled from the VUF used for MPE XL, the OS product.  In other words,
the Commercial Systems XL Release VUF reflects the level of change being
made in the release, not just to MPE XL.

The level of change to the release is the factor that determines how the
release VUF is modified.  This also corresponds to the name used to
identify the release type.

The following diagram illustrates how the release VUF is modified to
identify each release type.


 *  The position used to indicate an NL Build is also used to indicate a
    post-MR build.

Additional Notes: 

   1.  The following describes the characters used in the individual VUF
       positions and how they are incremented.

         A - Alphabetic characters only, starting with "A" and
         incrementing in alphabetical order.

         @ - Alphabetic and numeric characters.  Positions start with "0"
         and increment through "9" , then alphabetic characters are used
         starting with "A" and incrementing in alphabetical order.

   2.  This VUF nomenclature does not correspond to the nomenclature used
       for MPE V. Most notably is that the "Production Release" indicator
       is in the third character instead of the last.  However, the
       nomenclature does follow the HP corporate standards.  The greater
       the magnitude of change "to the release" , the farther left the
       change in the VUF.

EXAMPLES 

The following scenario provides an example of how the naming convention
and VUF nomenclature works for Commercial Systems XL Releases.

     A.01.20  - A Patch Build to A.01.00  (Release 1.0)
     A.01.21  - An NL Build to A.01.20    (Release 1.0)
     A.02.00  - A Production Release      (Release 1.0)
     A.02.10  - A Patch Build to A.02.00  (Release 1.0)
     A.10.00  - A Core Software Release   (Release 1.1)
     A.10.10  - A Patch Build to A.10.00  (Release 1.1)
     A.11.00  - A Production Release      (Release 1.1)

MPE/iX Communicators