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.

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)

Please note:

An example:

This example shows that the optiPoint 410/420 SIP V6.0 software release version 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) so it doesn't introduce any new minor feature enhancements.
- 62 (as Fix Release) so it introduces a collection of solutions to TRs and HFs
- 0 (as Hotfix) so it doesn't introduce any new immediate solution to just one TR or only few TRs

This new software version naming scheme does not imply any naming requirements 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:

opt410adv_SIP_6_0_62.exe containing:
- opt410adv_SIP_6_0_62.fli
- opt410adv_SIP_6_0_62.app

or whatever convenient for its correct usage.

It's not required nor mandatory that it's named exactly like the software version it's representing.

New Software Versioning scheme