Version numbering policies can be a bit crazy at times (see Version numbers and JSR277, or Oracle, with its Oracle Database 11g Release 2:
See also Software Versioning is Ridiculous).
But you can start by looking at the Eclipse Version Number policy as a good start.
If you really think you need more than three digits, this V.R.M.F. Maintenance Stream Delivery Vehicle terminology explanation is also interesting, but more so for post 1.0 software programs, where fix pack and interim fixes are in order.
- How to upgrade versions correctly
“Ship it already”:
Also known as the “
1.oh-oh” version. At least, it is out there, and you can begin to get feedback and iterate fast.
- Which is a good starting version number
0.x if major features are still missing;
1.0.0 if the major features are there.
- Is it ok to make numbers above 10? like v1.25 or v2.2.30?
Yes, but I would say only for large projects with a lifespan over several years (a decade usually)
Note that “correctly” (while being described at length in Semantic Versioning 2.0.0) can also be guided by more pragmatic factors:
See the announcement for Git 1.9 (January 2014):
A release candidate Git v1.9-rc2 is now available for testing at the usual places.
I’ve heard rumours that various third-party tools do not like the two-digit version numbers (e.g. “Git 2.0”) and started barfing left and right when the users install v1.9-rc1.
While it is tempting to laugh at them for their sloppy assumption, I am also practical and
do not mind calling the upcoming release v1.9.0 to help them.
If we go that route (and I am inclined to go that route at this moment), the versioning scheme will be:
- The next release candidate will be
- The first maintenance release for
v1.9.1(and Nth one be
- The feature release after v1.9.0 will be either v1.10.0 or v2.0.0, depending on how big the feature jump we are looking at.
Update Feb. 2019: semver itself is about to evolve (again, after semver2).
See “What’s next for SemVer”, and