Version numbering basics? [closed]

Answer 1

You can use any form of version numbering you desire.

I just recommend using something that makes sense. The Major.Minor.Revision numbering is popular, but any numbering scheme you wish is "valid".

Answer 2

It does not really matter, as long as you can use the version number to identify your versions (i. e. either add your source control system's internal revision number into the version number) or use it for tagging your releases.

When you do so, you might want to use that number as your third (or fourth) component. It looks confusing if some product jumps from version 1.12345 to 2.12346, but jumping from 1.4.12345 to 2.0.12345 is more common.

About which number to start, I just want to quote Eric S. Raymond:

In the closed-source world, Version 1.0 means "Don't touch this if you're prudent."; in the open-source world it reads something more like "The developers are willing to bet their reputations on this."

Answer 3

To the best of my knowledge, there is as yet no government agency dictating how you number versions. But don't worry, I'm sure it will come soon enough.

Ditto on those suggesting major-dot-minor-revision. My general approach is: Major changes get a new major version. Like, if we've added important new features. Small changes, like added some little convenience features or one new report, get a minor revision. Hot bug fix changes get a revision.

I would definately avoid calling your first published version "0.l" for simple marketing reasons: Numbers less than 1.0 sound like a preliminary version or a beta version. I've known people to call their first version 2.3 or some such just to make it sound like it's been around a little while to inspire more confidence, though that strikes me as a little dishonest.

Answer 4

You can use whatever numbers you want in your versioning - who's going to constrain you?

If you want your first version to be 0.0.0.0.0.0.0.1, that's fine, albeit a little silly. If you want your first version to be 106.3, you can do that too, but that's a little more ridiculous.

Check out the Wikipedia article on Software Versioning for some tried-and-true ideas of realistic version numbering schemes.

Answer 5

how about the software which is not distributed to public like a webmail source code? do you think that the build or bug fix number is still important in this case?

Answer 6

Most places use something like this:

Major Release.Minor Release.Hot Fix.Build

Your version numbers would look like 1.5.0.15, etc.