| || |
The patch number
For version number, there is a format, like 1.31. The 1st digit means a huge change. The 2nd digit means some new features. The 3rd digit means the patch(hot fix). Is this correct?
Any other recommandation?
Re: The patch number
Version nos/ Build nos could follow a varity of patterns. Each organization has its own rules for the same.
For eg a version could be something like:
Foo 1.21.118 or Foo 22.214.171.124.2
Depending on your build numbering system and your configuration management procedures you could come up with some rules for the same.
You could even have the build number in the version no.:
where 1 is the major version.
21 could be the minor release version
1 could be the patch number
and 117 could be the build number
So depending on the way you define your rules you could set a good process for it. All you need to remember is to make sure that there is no ambiguity while implementing the same.
Best of Luck,