Getting software version numbers right. v1.0.0.1 [closed]

Answer 1

I usually use D as a build counter (automatic increment by compiler) I increment C every time a build is released to "public" (not every build is released) A and B are used as major/minor version number and changed manually.

Answer 2

People tend to want to make this much harder than it really needs to be. If your product has only a single long-lived branch, just name successive versions by their build number. If you've got some kind of "minor bug fixes are free, but you have to pay for major new versions", then use 1.0, 1.1 ... 1.n, 2.0, 2.1... etc.

If you can't immediately figure out what the A,B,C, and D in your example are, then you obviously don't need them.

Answer 3

For the past six major versions, we've used M.0.m.b where M is the major version, m is the minor version, and b is the build number. So released versions included 6.0.2, 7.0.1, ..., up to 11.0.0. Don't ask why the second number is always 0; I've asked a number of times and nobody really knows. We haven't had a non-zero there since 5.5 was released in 1996.