Release Numbering Process: It won’t be the same for all companies... But generally it will be so... :)
Each product will have series of product releases. A product release will have a generic four integer identifier (product release number) A, B, C, D where
A, B, C, D are integers
A corresponds to Major / Marketing release version. (significant change in product.)
B corresponds to Minor release version. (major functional changes)
C corresponds to Servicepack release version. (service pack identifier with small bug fixes)
D <= 9 corresponds to Special release version (exceptional case where one or two files will be updated after offcial product release)
Based on the above definition the three aspects of product release numbering conventions to be followed are,
Major / Marketing Release Version - A
Engineering Release Version - A.B.C
Build Number - ABC[0-9]
Examples
Eg-1) If release version of a product is 4.0.0 then by default the Build Number at about dialog will be Build 4000
If release version of a product is 4.0.0 and if the release contains one special update then the Build Number at about dialog will be Build 4001
If release version of a product is 4.1.0 then by default the Build Number at about dialog will be Build 4100
If release version of a product is 4.1.2 then by default the Build Number at about dialog will be Build 4120
Eg-2) If build number of a product is 5342 then
5 - Major / Marketing release version.
3 - Minor version
4 - Service Pack Version
2 - Special updates. There should not be more than 9 special updates.
Eg-3) Product Name>_5.0.0 New general major release.
No comments:
Post a Comment