Chandler Version Number

It's best to do this by example. Assuming we are working towards 0.7 release, we could have the following "milestones": 0.7alpha1, 0.7alpha2 and so on until we release 0.7.

While we are working on a milestone, we do continuous builds, and those are identified by appending ".dev-rXXX" to the end of the milestone number we are working towards (without quotes and where XXX is the subversion revision number). So for example 0.7alpha1.dev-r1111.

We also have weekly checkppoints that are identified by appending "-checkpointYYYYMMDD" to the end of the continuous build version number (without quotes and where YYYY is the current year, MM the month, DD the day). For example 0.7alpha1.dev-r1111-checkpoint20060219.

Here is another example of how versions would compare and how they would appear in a timeline: 0.7alpha1.dev-r1111 -> 0.7alpha1.dev-r1111-checkpoint20060219 -> 0.7alpha1 -> 0.7 -> 0.7.1 ...

This scheme is compatible with the Python egg version parsing routines. For more information, see http://peak.telecommunity.com/DevCenter/setuptools#specifying-your-project-s-version.