Cisco Cisco Packet Data Gateway (PDG)
System Operator Notes
▀ StarOS Version Numbering System
▄ Release Change Reference, StarOS Release 16
640
StarOS Version Numbering System
The output of the show version command displays detailed information about the version of StarOS currently running
on the ASR 5x00 or QvPC platform.
on the ASR 5x00 or QvPC platform.
Prior to release 16.1, the Image Version version field displayed a branch of software including the build number, for
example “16.0 (55435)”. Subsequent releases of software for the major release differed only in build number. Lab
Quality/EFT releases versus deployment releases also differed only in build number.
example “16.0 (55435)”. Subsequent releases of software for the major release differed only in build number. Lab
Quality/EFT releases versus deployment releases also differed only in build number.
From release 16.1 onwards, the output of the show version command, as well as the terminology used to describe the
Build Version Number fields, has changed. Additionally, show version will display slightly different information
depending on whether or not a build is suitable for deployment.
Build Version Number fields, has changed. Additionally, show version will display slightly different information
depending on whether or not a build is suitable for deployment.
The Version Build Number for 16.1 and onwards releases now include, at minimum, a major, maintenance, and
emergency release number, for example “16.1.2”. The appropriate version number field increments after a version has
been released. The new version numbering format is a contiguous sequential number that represents incremental
changes between releases. This format will facilitate identifying the changes between releases when using Bug Toolkit
to research software releases.
emergency release number, for example “16.1.2”. The appropriate version number field increments after a version has
been released. The new version numbering format is a contiguous sequential number that represents incremental
changes between releases. This format will facilitate identifying the changes between releases when using Bug Toolkit
to research software releases.
The following diagram shows the differences between the old numbering format and the new numbering format.
Figure 3.
Comparison of Old and New StarOS Version Numbering Formats
In the old format, the first two fields of the Build Version Number represented the Major release and subsequent
releases (MRs/ERs) would differ only by build number. Documentation references to a release included descriptive text
to indicate whether the release was an MR or ER. For instance, “16.0.65781 MR1” indicates via its descriptor that it is
the first maintenance release for 16.0.
releases (MRs/ERs) would differ only by build number. Documentation references to a release included descriptive text
to indicate whether the release was an MR or ER. For instance, “16.0.65781 MR1” indicates via its descriptor that it is
the first maintenance release for 16.0.
In the new format, the maintenance release number changes with subsequent Maintenance Releases (MRs). For
example, “16.2” would represent the second maintenance release (MR2) of release 16.
example, “16.2” would represent the second maintenance release (MR2) of release 16.
A third digit in the Build Version Number now indicates an Emergency Release for a previous FCS or MR build. For
example “16.1.3” indicates the third ER of the first MR of the 16.0 major release.
example “16.1.3” indicates the third ER of the first MR of the 16.0 major release.
The Build Version Number may now also include an optional variant indicator just before the ER number to identify the
release as a variant of an MR or ER Release. A variant release is one that is given to a particular customer or group of
customers, as opposed to a mainstream release which is suitable for all customers.
release as a variant of an MR or ER Release. A variant release is one that is given to a particular customer or group of
customers, as opposed to a mainstream release which is suitable for all customers.