Code version change "rules"

Question

Hi guys,

First of all, i know that there are no fixed rules about software version control but I have several questions.

1) How to upgrade versions correctly

I have a small software that I started a while ago and since i started from scratch I started with version 0.1.

As I added more functionality I have been upgrading the minor number. Now Im in v0.5.7 (minor (.5) for new functions and revision (.7) for bug fixes and minor changes), the thing is that the program is almost complete for distribution, but now im "missing" several minor versions, how do you guys handle that situation? do you simply just jump the numbers?

That brings me to the second question.

2) Which is a good starting version number

I am about to start a new project. This time is not that small of a project and is going to be public and free for modifying, I do not want to have the issues mentioned above. So which would be a good starting point?

Bonus question:

3) Is it ok to make numbers above 10? like v1.25 or v2.2.30?

I haven't seen software with that kind of numbering (probably they show it only in the help section or in their web-page), again I am aware that there are no rules for that but it seems to be that there is a general consent on how to keep the version numbers.

Thanks in advance for all your help.

-RaptorX

Answer 1

Version nubering policies can be a bit crazy at times (see Version numbers and JSR277, or Oracle, with its Oracle Database 11g Release 2: 11.2.0.1.0.
See also Software Versioning is Ridiculous).

But you can start by looking et 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 softwares, where fix pack and interim fixes are in order.

---

1/ "Ship it already": 1.0.0

Also known as the "1.oh-oh" version. At least, it is out there and you can begin to get feedback and iterate fast.

2/ 0.x if major features are still missing; 1.0.0 if the major features are there.

3/ Yes, but I would say only for large projects with a lifespan over several years (a decade usually)