Difference between revisions of "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.
(→Examples: (Added a second F) |
m (Some text revised and examples added) |
||
| Line 30: | Line 30: | ||
=== Examples === | === Examples === | ||
| + | |||
| + | ==== new Minor Release ==== | ||
| + | |||
| + | A new Minor Release was released:<br/> | ||
| + | |||
| + | |||
==== new Fix Release ==== | ==== new Fix Release ==== | ||
| Line 59: | Line 65: | ||
** 31 (as Fix Release) means it introduces a ''collection of solutions to TRs and HFs'' | ** 31 (as Fix Release) means it introduces a ''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'' | ** 0 (as Hotfix) means it doesn't introduce any new ''immediate solution to just one TR or only few TRs'' | ||
| + | <br/> | ||
| + | |||
| + | ==== new Hotfix Release ==== | ||
| + | |||
| + | A new Hotfix Release (HF) was released:<br/> | ||
| + | |||
| + | * Product Name : optiPoint 410/420 SIP V6.0 | ||
| + | * Software Version : V6 R0.62.1 | ||
| + | <br/> | ||
| + | Compared to a software version previously released (if any), the one considered:<br/> | ||
| + | |||
| + | * Refers to Version V6 (as Major Release), the additional .0 could be omitted in this case (so V6 is equal to V6.0). | ||
| + | * Refers to 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 ''immediate solution to just one TR or only few TRs'' | ||
<br/> | <br/> | ||
=== Warning === | === Warning === | ||
| − | {{Info|This new software version naming scheme does '''not''' imply any naming requirements for: | + | {{Info|This new software version naming scheme does '''not''' imply any naming requirements / rules for: |
* Application files | * Application files | ||
| Line 79: | Line 101: | ||
or whatever convenient for its correct usage.<br/> | or whatever convenient for its correct usage.<br/> | ||
| − | + | 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.}} | |
Revision as of 11:31, 20 December 2006
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.
- 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
Please also note that Version (Major) and Release (Minor, Fix and Hotfix) give both absolute and relative informations about a specific software's feature/bugfix levels but it's also necessary to compare them to previous ones to understand exactly what's new or different.
More in the examples below.
Examples
new Minor Release
A new Minor Release was released:
new Fix Release
A new Fix Release (FR) was released:
- Product Name : optiPoint 410/420 SIP V6.0
- Software Version : V6 R0.62.0
Compared to a software version previously released (if any), the one considered:
- Refers to Version V6 (as Major Release), the additional .0 could be omitted in this case (so V6 is equal to V6.0).
- Refers to 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 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
A new Fix Release (FR) was released:
- Product Name : optiPoint 150 SIP V1.0
- Software Version : V1 R0.31.0
Compared to a software version previously released (if any), the one considered:
- Refers to Version V1 (as Major Release), the additional .0 could be omitted in this case (so V1 is equal to V1.0).
- Refers to 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 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
A new Hotfix Release (HF) was released:
- Product Name : optiPoint 410/420 SIP V6.0
- Software Version : V6 R0.62.1
Compared to a software version previously released (if any), the one considered:
- Refers to Version V6 (as Major Release), the additional .0 could be omitted in this case (so V6 is equal to V6.0).
- Refers to 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 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. |
