Version Strings

The version strings have changed a little to cope with the multiple branching that git enables.

Released versions

For released tar.gz coming from sf.net, nothing is changed : it's a plain revision number such as 2.0.1.

Example : 2.0.1

master branch

Here we just take the latest revision number and append to it :

• the number of commits since the latest release.
• the first 7 hex SHA1 char of the last commit.

Example : 2.0.1-21-g2c15cad

The rationale is that the master branch follows quite closely released version, so we'd like to know which release it was based on.

Any other branch

It can be devel or a feature-based one such as my-new-feature.

Here we take, in order :

• the branch name
• the date of the last commit.
• the first 7 hex SHA1 char of the last commit.

Example : devel-2012-06-08-dd7f3c9c or my-new-feature-2012-06-05-69a3159.

The rationale is that other branches don't follow closely a released version. But we'd still like to know how old the code was, that's why there's a commit date instead of a number of commits.

Note that it has no real meaning to directly compare 2 version strings of unrelated branches together, expect from code age.