What the numbers mean

Version numbers

Our way of numbering software versions is very similar to how Linux kernels are done.

Full Version Number
A full, three-part number indicating a specific implementation. This is specified in a.b.c format.

Major Release Number
The first number is the major release number (that's the a). All beta software will start with 0. Once the software is ready for a first release it will be go up to 1: ie. 1.0.0. And every major rewrite of the software will increment by one.

A major release should have a high-level set of specific goals that it is meeting. For Da'ath 1.0, this was the reaching of a final stable release. For later versions, this may include implementation of more modular approach, a templating system for the user-interface, and so forth.

Minor Release Number
The second number is the minor release number (that's the b). The minor release number will tell you whether a release is a stable or development branch. Even numbers (0, 2, 4...) mean that it's a stable release, and odd numbers (1, 3, 5...) mean it's a development release.

A minor release should have a lower-level set of specific goals that it is meeting. These goals should, somehow or another, be a subset of the goals for the major release of which it is a part. Basically, the minor releases allow for the major goals of a major release to be broken into a more discrete, attainable set of objectives.

Release Increment-or
Lastly, the final number in a three-part version number is a release increment-or (that's the c). In a stable branch, new versions will be release as bugs are found and squished. In a development branch, new versions will be released as progress is made toward the goals set for the next major and minor release. New releases will happen as needed in a stable branch. In a development branch, however, they should happen frequently, as more progress is made toward the next minor release.