LenMus version numbering scheme

The LenMus version numbering scheme is simple: just two numbers (i.e. "3.0"). The first one is the major number and the second one is the revision number.

Major number
It is incremented when a program change affects to a significative part of the code. It takes place normally only due to internal architectural re-design.

Revision number
It is incremented when a new package is released.

In addition, if the release is not an stable version, with all planned functionality and tested enough, it will be followed by a pre-release identification code (i.e. "a3") formed as follows:

Pre-release letter
a
Alpha version. This is a snapshot of current development. The version is operative but not all planned functionality is yet included. Also it contains bugs and unfinished code.
b
Beta version. It is an operative finished version, that is, it includes all planned functionality. But it is in testing phase and so it might contain bugs.

Pre-release number
Just a sequential number to identify the pre-release

Alpha pre-releases will normally take place only when the version major number changes. Beta pre-releases are launched only when the new code is complex enough as to requiere an extensive testing phase. So, for example, if the move from version 5.3 to version 5.4 does not require a long testing phase, there will be no 5.4.b0 pre-release.

Examples