Version numbering basics? [closed]

Answer 1

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

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 4

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 5

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.

Answer 6

I seem to remember that in the old days (I am talking Commodore here) we used a syntax like release.version.revision which could be appended with either fix and/or build, where fix would usually be a letter stuck directly to the revision. So a full number would read something like:

2.1.44a.786

But like most have already said, it doesn't really matter, there is no true standard for this. Just use whatever is most convenient for you.