Certainly, it's actual the Microsoft Windows format for version numbers. When you make a tiny change to a program to fix a bug then you make a new
build and update the
build number. The build number updates each time the program is built again. When you've made a number of builds or you make a backwards incompatible change then you should make a new
release and increment the
release number. After so many releases you should make a
minor release and increment the
minor revision number. And when you've made enough minor releases you should finally make a
major release, the difference between GM7 and GM8, and increment the
major version number.
Major.Minor.Release.Build
Is also what I've been kind of following for LGM changes. Just not as strictly. Like for instance how I'm working on 1.8.7 after 1.8.6.xxx as well as 16b5.
https://en.wikipedia.org/wiki/Software_versioninghttps://en.wikipedia.org/wiki/Microsoft_version_numbering