I think more people are starting to use semantic versioning: http://semver.org/
The gist of it is: Given a version number MAJOR.MINOR.PATCH, increment the:
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.
This way the numbers actually mean something in a somewhat consistent way across programs. npm packages use this for example.
Slashdot Mirror
I think more people are starting to use semantic versioning: http://semver.org/
The gist of it is:
Given a version number MAJOR.MINOR.PATCH, increment the:
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.
This way the numbers actually mean something in a somewhat consistent way across programs.
npm packages use this for example.