Common schemes for version numbering:
Usage: You know what you do and do not plan to do more once finished. Or you got bored and put the versions out even though everything was finished long ago.
- Dev Cycle Mode:
- 0.1 alpha
- 0.1 beta
- 0.1
- 0.2 alpha
- ...
- 0.23 alpha
- 0.23 beta
- 0.23
- 1.00 alpha
- 1.00 beta
- ...
- 2.something
- ...
Usage: You start implementing a feature update, for each a sub-version behind the dot. Once completed, the next feature update gets the higher number
- The Hipster Way:
- 1703
- 1709
- 1803
- ...
- 2003
- 2009
- ...
Usage: Someone did that and you have to do it the same fancy way for your half-yearly releases because it's hip. Shit only that something looks odd in the years 2019 and 2020. But heads up! 2021 is coming!
- The Windows Way:
- I won't comment on that. Some versions are legendary good, some legendary bad. The numbers don't follow a common scheme so that it's difficult to find a consensus what version actually was good, or bad.
After a while, you lose interest in finding new version numbers, so you stick to the last one and change the version scheme to something fancy (see previous way).
- The Google Way:
- Cupcake
- Donut
- Eclair
- ...
- Kitkat
- ...
- Oreo
- Pie
- ...
Usage: You plan 26 releases.
- The Firefox Way:
- 1.something
- One year later 2.something
- One year later 3.something
- One year later 16.something (WTF?)
- One year later 36.something
- One year later 75.something
Usage: If I only knew...
Usage: Never