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

Most places use something like this:

Major Release.Minor Release.Hot Fix.Build

Your version numbers would look like 1.5.0.15, etc.

Answer 2

Version numbers are not a concrete specification in software development.

In other words, one team may use 1.0.0.0, others may use 1.0.0 and so on. It matters not.

Just choose something that works for you.

Typically major.minor.revision is the most simple and straight forward method to use. Visual Studio for example can assign version numbers automatically for you, as can other tools. So all you are required to update is the major/minor values. The build/revision numbers are updated automatically.

Answer 3

I've used

Major.Minor.Release.Build 1.02.4.15

and also

Year.Month.Date

2009.12.10

but anything that allows you to individually track releases would work. As long as you're consistent.

Answer 4

You might want to start by taking a look at the Software versioning article on wikipedia, which gives some informations about the possibilities you have ;-)

It might give you some ideas of what you could do in your specific case...

Answer 5

10.50.1600.1
major.minor.build.revision

MAJOR changes is backward incompatible and require changing project name, path to files, GUIDs, etc.

MINOR changes is backward compatible. Mark introduction of new features.

REV for security/bug fixes. Backward and forward compatible.

eg. In SQL server 2008 RTM version number is 10.00.1600.22 and In SQL server 2012 version is 11.00.2100.60

First field is changed due to change in project name i.e. 10 and 11

In SQL server 2008 R2 RTM version number is 10.50.1600.1 and In SQL server 2008 version is 11.00.1600.22

Second field is changed due to introduction of new features.

Third field indicate build(developed)

Forth field indicates revision i.e. hotfixes applied...

Answer 6

Take a look here. python setuptools has a very interesting and clear specification for version numbering. I'm sure you can obtain some very insightful hints from it.