Version numbering basics? [closed]

Question

Suppose I have a web application with some basic functions. I want to market it. So I would like to assign a version number - something like 0.0.1. What I want to know is are there any constraints that should apply to that numbering system?

Hope you understood my question, thanks in advance.

Answer 1

We use major.minor.revision.build where revision is the SVN revision and build is the build number which is based on the current date (in YYDDD format where YY is the year and DDD the day number, so 18001 would be Jan 1st 2018.)

Having the SVN revision is incredibly useful and has saved us on more than one occasion.

Answer 2

A lot of free software uses a three point system: X.Y.Z where

• X is for compatibility breaking releases.
• Y is for other releases, with even numbers being stable and odd numbers being unstable.
• Z is for fixes.

This way version 0.28.1 is a stable release with one fix and 2.9.0 is an alpha release with zero fixes.

Some people also have fun developing their own schemes. E.g. Tex which by each release approxed Pi, with version numbers: 3, 3.1, 3.14, etc.

Answer 3

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 4

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 5

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."