Release Policy

Version numbering

From version 0.8 on we'd like to use the following numbering scheme: a.x.y.z

This may sound ridiculous first, but has some certain meaning that fits into the project's generation process. The variables a, x, y, z are of course version and subversion numbers and are meant to have the following meanings:

• a: The major release number;
  actually we do not suppose to get over zero until the end of this year as one of the simulation's major features - the multimodality - is not yet implemented
• x: The minor release number;
  indicates the closure of some subwork (such as multithreading, new detector scheme atc.), so you can expect some new features
  Furthermore, you can also expect that some of the used formats change.
• y: The subrelease number indicating that some new features are available but possibly not fully developed and the some of the formats used have changed.
• z: The subrelease number indicating that some new features are available but possibly not fully developed and the some of the formats used have NOT changed.

So the major reason for such a complicated procedure is that during the development at such an early stage, some of the formats used, for example the one for the network change over time. This requires a rebuilding/reconversion of the networks used.
There is no possibility to avoid it, in fact, but at least we want to provide our user's information about the necessarity to do it.

Release period

We will try to increase the frequency in comparison to the past and to release a subrelease once a month. If you want to keep absolutely up to date, we advice you to use the sources from the cvs archive which are compileable and running in most cases.