Michael Kolb Fulda» Web Engineering http://www.michael-kolb.co.uk Web Engineering Mon, 01 Mar 2010 05:58:27 +0000 http://wordpress.org/?v=2.9.1 en hourly 1 How to arrange a software version number http://www.michael-kolb.co.uk/engineering/how-to-arrange-a-software-version-number/ http://www.michael-kolb.co.uk/engineering/how-to-arrange-a-software-version-number/#comments Sun, 08 Feb 2009 18:30:55 +0000 mk_michael http://www.michael-kolb.co.uk/?p=1069 Version numbers defines different software versions in the development process. In a constantly software development, which takes a lot of years, it’s essential to define a fixed number which represents a release.

But what is a meaningful arrangement of such a version number? For projects developed by my own, I’m using this arrangement:
versionnumber

But there are a lot more arranges you can use. Especially for bigger projects, with a couple of developers, the kind above will be insufficient. So a build number is always a good idea, like:


<major release>.<minor release>.<patch level>-<build number>
Example: 2.3.5-0041

Major release: Very significant changes, for example a new engine or changed API’s.
Minor release: New functions and features.
Patch level: Fixed bugs
Build: The amount of compiled versions

Please feel free to comment any different arrangements you know.

]]> http://www.michael-kolb.co.uk/engineering/how-to-arrange-a-software-version-number/feed/ 4