Software Version Numbering Standards. The most common numbering requirements are based on historical work methodologies specific industry requirements and compliance standards. If you line up all versions of a product from the original to the most recently updated version you will be able to tell the order in which they were released by looking at the version numbers.
It is automatically incremented by the build process every time it runs. Stick to a simple MAJORMINOR release system like v127 where MAJOR is the compatibility level version 2x is incompatible with or at least majorly different from version 1x and MINOR is your bugfix releases or minor enhancements. But software version numbers even arbitrarily detailed programmer version numbers cant seem to avoid dates either.
The most interesting thing to watch for is the first 4-digit number you encounter.
MAJOR version when you make incompatible API changes MINOR version when you add functionality in a backwards compatible manner and PATCH version when you make backwards compatible bug fixes. In some cases the use is a direct analogy for example. Stick to a simple MAJORMINOR release system like v127 where MAJOR is the compatibility level version 2x is incompatible with or at least majorly different from version 1x and MINOR is your bugfix releases or minor enhancements. Version numbers follow these guidelines.