Semantic Versioning
Major, Minor, Patch
- 0.1.0
- 0.1.1
- 0.2.0
- 1.0.0
Tags
- v1.3.0
- v1.4.0
Linux Kernel
- 2x: 2.6.MINOR.BUGFIX -> 2.6.39
- 3x: 3.MINOR.BUGFIX -> 3.19
- 4x: 4.MINOR.BUGFIX
TeX
Nähert sich Pi an.
- 3.1
- 3.14
- …
- 3.14159265I
Commit suffix
- 1.2-c37d2e
OpenBSD
Release Zyklus jedes halbe Jahr. Einfaches hochzählen.
- 5.2
- 5.3
- 5.4
- …
- 5.9
- 6.0
Release Date
Perforce zum Beispiel
- 3.1.20121204
- 3.1.20121504
oder
2016/01
tzdata
- tzdata2015f
- tzdata2015g
- tzdata2016a
- tzdata2016c
- tzdata2016d
Negative Zahlen
Some projects use negative version numbers. One example is the SmartEiffel compiler which started from -1.0 and counted upwards to 0.0.[10] – Wikipedia
Blöde Zahlen überspringen
Auch wird gerne mal die 13 übersprungen
Nokia decided to jump directly from S60 3rd Edition to S60 5th Edition, skipping the fourth edition due to the tetraphobia of their Asian customers. – Wikipedia
OpenSSL
lol.
- 0.9.1a
- 0.9.1b
- 1.0.0
- 1.0.0a
- 1.0.1
- 1.0.1a
- 1.0.2
Overengineered
Our R&D department uses 1.0.0.0.0.000: MAJOR.minor.patch.audience.critical_situation.build Please, please, don’t do that. – Stackoverflow
Mediawiki
- 1.7.0,
- 1.8.0,
- 1.8.1,
- 1.9.0,
- 1.10.0,
- 1.11.0,
- 1.11.1,
- 1.11.2