New Software Versioning scheme
The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.
Contents
What's new
The new software versioning scheme rules each application software to be named as:
V x[.y] R m.f.h
Where V and R stand for:
- V = Version
- The Version field is identified by:
- x = Major Release as result of major feature enhancements with M3 status of product (as new product version).
- y = as an optional additional numbering.
- The Version field is identified by:
- R = Release
- The Release field is identified by:
- m = Minor Release as result of minor feature enhancements (covers TRs and CRs)
- f = Fix Release (FR) as result of a collection of solutions to TRs and HFs (covers only TRs, no CRs)
- h = Hotfix (HF) as result of immediate solution to just one TR or only few TRs and to all TRs for Focal and/or Hot accounts (a Hotfix comprises all previous HFs, as example those cumulated since the latest FR)
- The Release field is identified by:
Please note:
- FR = Fix Release
- HF = Hot Fix
- TR = Trouble Report
- CR = Change Request
- Major, Minor and Fix (FR) releases are relevant for manufacturing purposes
- Hotfix release (HF) is relevant for Service Level 2 support only
Please also note that Version (Major) and Release (Minor, Fix and Hotfix) fields give both absolute and relative informations about a specific software's feature / bugfix levels so it's necessary to compare them both to immediately previous ones and to older versions to understand exactly what's new, what was enhanced or what's different.
More in examples below.
Examples
new Major Release
Compared to a software version previously released (if any), a new Major Release (and consequently Minor too):
Product Name | Version (Major) | Release (Minor, Fix and Hotfix) | Previous Version | Previous Release |
---|---|---|---|---|
HiPath 3000 V6.0 | V6.0 | Rx.x.x (x means any number) | V5.0 or older | Any |
is available and refers to both a new product Version V6.0 (as Major Release) and a new related Minor release, so:
- 6 (as Major Release) means it introduces new major feature enhancements.
- Rx.x.x (as Minor Release mainly) means it introduces new minor feature enhancements
- Fix (FR) and Hotfix (HF) releases could then follow or could be immediately present (it should depends to development status when the M3 is declared)
new Minor Release
Compared to a software version previously released (if any), a new Minor Release:
Product Name | Version (Major) | Release (Minor, Fix and Hotfix) | Previous available |
---|---|---|---|
HiPath 3000 V6.0 | V6.0 | R8.0.0 | R7.x.x (x means any number) or older |
is available, it:
- refers to product Version V6 (as Major Release), the additional .0 could be omitted in this case (so V6 is equal to V6.0).
- refers to product Release R8.0.0:
- 8 (as Minor Release) means it introduces new minor feature enhancements.
- 0 (as Fix Release) means it doesn't introduce any new collection of solutions to TRs and HFs.
- 0 (as Hotfix) means it doesn't introduce any new immediate solution to just one TR or only few TRs.
new Fix Release
Compared to a software version previously released (if any), a new Fix Release (FR):
Product Name | Version (Major) | Release (Minor, Fix and Hotfix) | Previous available |
---|---|---|---|
optiPoint 410/420 SIP V6.0 | V6.0 | R0.62.0 | R0.61.x (x means any number) or older |
is available, it:
- refers to product Version V6 (as Major Release), the additional .0 could be omitted in this case (so V6 is equal to V6.0).
- refers to product Release R0.62.0:
- 0 (as Minor Release) means it doesn't introduce any new minor feature enhancements.
- 62 (as Fix Release) means it introduces a new collection of solutions to TRs and HFs.
- 0 (as Hotfix) means it doesn't introduce any new immediate solution to just one TR or only few TRs.
Compared to a software version previously released (if any), a new Fix Release (FR):
Product Name | Version (Major) | Release (Minor, Fix and Hotfix) | Previous available |
---|---|---|---|
optiPoint 150 SIP V1.0 | V1.0 | R0.31.0 | R0.30.x (x means any number) or older |
is available, it:
- refers to product Version V1 (as Major Release), the additional .0 could be omitted in this case (so V1 is equal to V1.0).
- refers to product Release R0.31.0:
- 0 (as Minor Release) means it doesn't introduce any new minor feature enhancements.
- 31 (as Fix Release) means it introduces a new collection of solutions to TRs and HFs.
- 0 (as Hotfix) means it doesn't introduce any new immediate solution to just one TR or only few TRs.
new Hotfix Release
Compared to a software version previously released (if any), a new Hotfix Release (HF):
Product Name | Version (Major) | Release (Minor, Fix and Hotfix) | Previous available |
---|---|---|---|
HiPath 3000 V6.0 | V6.0 | R8.0.1 | R8.0.0 or older |
is available, it:
- refers to product Version V6 (as Major Release), the additional .0 could be omitted in this case (so V6 is equal to V6.0).
- refers to product Release R8.0.1:
- 8 (as Minor Release) means it doesn't introduce any new minor feature enhancements.
- 0 (as Fix Release) means it doesn't introduce any new collection of solutions to TRs and HFs.
- 1 (as Hotfix) means it introduces a new immediate solution to just one TR or only few TRs.
Compared to a software version previously released (if any), a new Hotfix Release (HF):
Product Name | Version (Major) | Release (Minor, Fix and Hotfix) | Previous available |
---|---|---|---|
optiPoint 410/420 SIP V6.0 | V6.0 | R0.62.1 | R0.62.0, R0.61.x (x means any number) or older |
is available, it:
- refers to product Version V6 (as Major Release), the additional .0 could be omitted in this case (so V6 is equal to V6.0).
- refers to product Release R0.62.1
- 0 (as Minor Release) means it doesn't introduce any new minor feature enhancements.
- 62 (as Fix Release) means it introduces a collection of solutions to TRs and HFs
- 1 (as Hotfix) means it introduces a new immediate solution to just one TR or only few TRs
Warning
This new software version naming scheme does not imply any naming requirements / rules for:
related to each Software Applications considered. This means that, referring to the example above, the software (Application, Firmware or Loadware) file / files could be named as:
or whatever convenient for its correct usage. Even if often Application / Loadware / Firmware file names reflect product software revision levels, it's not required, nor mandatory, that they were named to reflect exactly the software version they're representing. |