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:
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.
Versionierung von Software | webdesign joomla online business marketing geeks und das web 2.0
February 13th, 2009
[...] einen Überblick über die Versionen zu bewahren empfiehlt Michael zum Beispiel für datenbankbasierte (größere) Projekte folgende [...]
Kevin Godden
February 12th, 2009
Ha Ha, I have seen it before!
mk_michael
February 12th, 2009
If this happens I wil use v2.03.14za
Kevin Godden
February 12th, 2009
Hi Michael, I infer from your revision number format (detailed above) that you have been lucky enough not to have had more than 26 hot fix releases in a run!