This wiki is archived and useful information is being migrated to the main bzflag.org website
Difference between revisions of "BZFlag Version Numbers"
m |
|||
| Line 18: | Line 18: | ||
The value of a version number can and has gone over the value of 9 ( as in 1.10.0 ). The are treated as separate values. | The value of a version number can and has gone over the value of 9 ( as in 1.10.0 ). The are treated as separate values. | ||
| + | |||
| + | [[Category:Versions]] | ||
Revision as of 18:00, 6 April 2007
BZFlag uses a specific version numbering system for it's development and releases.
Overview
All BZFlag software is versioned. This allows easy identification of exactly when software was made, released, and what features it contains.
Version number Parts
BZflag version numbers are made up of 3 parts.
major version. minor version. revision
All 3 parts are numeric values.
Development versions are marked with ODD minor version (1.11.x, 2.1.x, etc..) Release versions are marked with EVEN minor version ( 1.10.x, 2.0.x, 2.2.x, etc..)
The revision number is used to represent changes in a specific minor version line. For development versions the minor revision is simply incremented as the development progresses, often when a major feature, or an incompatable networking protocol change is made. For release versions, the revision is set to an EVEN number for published releases, and set to an ODD number for maintenance work on a released codebase, ( i.e. 2.0.0 was a published release, bug fixes were done in the 2.0.1 version, then published as 2.0.2).
The value of a version number can and has gone over the value of 9 ( as in 1.10.0 ). The are treated as separate values.
