SahanaPy Version Numbering

Version numbering follows the following schema:

  [major].[minor].[version]-[branch]-[commit]

major	Major Release Number, starting with 0
minor	Minor Release Number, starting with 1
version	Release Version, even numbers = stable version, odd numbers = development version
branch	Name of the branch, omit for main trunk
commit	Branch commit number, omit for stable versions

Each new minor release starts with version number 0 in the stable, and 1 in the development version, i.e.:

• 0.3.0 is the initial stable version of the 0.3 release
• 0.3.1 is the initial development version of the 0.3 release

For each update of the stable version, both numbers are increased by 2, i.e. when 0.3.1 is tested and ready for release, then

• 0.3.1 gets renumbered as 0.3.2 for release (stable 0.3.0=>0.3.2)
• new development version will be 0.3.3 (development 0.3.1=>0.3.3)

E.g.:

0.3.3-haiti-567

• Major Release: 0
• Minor Release: 3 ("Banwell")
• Version: 3 (development version)
• Branch: haiti (Haiti Earthquake 2010 Deployment Branch)
• Commit No.: 567

0.3.4-haiti

• Major Release: 0
• Minor Release: 3
• Version: 4 (stable version, no commit number!)
• Branch: haiti (Haiti Earthquake 2010 Deployment Branch)

0.3.6

• Major Release: 0
• Minor Release: 3 (Codename "Banwell")
• Version: 6 (stable version, main trunk)