Version Numbering is important to
maintain asthis maintains the integrity of the code,
thus no two builds wil have the same version number
If we accept defining the numbering as in
A.b.c.d
- A
– Major Version, May have impact on other systems
- b
– Minor Version, Changes to functionality but no impact on
other systems
- c
– Maintenance version, Bug fixes only and no
changes
- d
– Build version,
We could skip the Build version
and just use 3 digits when in general release. (A.b.c)
In Normal operation each release will increment
the Minor Version ‘b’, Any interim releases would
increment the Maintenance Version ‘c’ this may
include fixes found during testing. the build version
‘d’ would increment with each build e.g.
- 5.3.0.24
first release
- Bugs
found so next release candidate is 5.3.1.7 etc. (7 builds Before
Release to SIT)
- More
bugs found and fixed so next release candidate would be
5.3.2.4
-
And so on
the numbering of versions should be such that the
Maintenance version ‘c’ and Minor Version
‘b’ number changes only when the code leaves System
test and goes to SIT, Multiple attempts that go to SIT would just
change the build version ‘d’ bugs found in SIT,
UAT etc. would increment the Maintenance Version
