Numbering

We use only 2 digits, then a reliability level, and finally possibly a sequential number.

Example :

1.2-Stable
1.1-Stable-1
1.2-Beta-2
1.2-Release-candidate-1
1.4-Alpha-1

In alpha versions, the last digit changes at least every time the structure of the database changes only after creation or modification of a table, a field, a constraint or any other object. In other versions, it changes in these cases and also every time a package of installation is published on SourceForge.

Reliability level

Alpha versions

Versions in development, not finished, which can contain several severe bugs and possibly destroy datas.

They are still build with sources contained in the trunk branch. No binary installer will be uploaded on SourceForge for these versions.

Never use them for real management, only on a copy of a test database.

You can indicate anomalies, if you are developer and verified that the corresponding sources have not just been archived.

Beta versions

They are versions at the end of development, possibly containing still bugs, and that must be tested. Normally, we do not add features at this level.

They are still build with sources contained in the trunk branch. Binary installation package of these versions are uploaded on SourceForge.

Do not use them for a real management, use them only on a copy of a database created and succesfully used with the last stable version.

Please, indicate any anomaly you found on the forum.

Release candidates

They are almost totally debugged versions, requiring more tests. We do not add any new feature at this level.

You can use them carefully for a real management, but only after having made a backup of the database and being sure to know how you can restore in case of issues.

Naturally, indicate errors found on the forum. Improvements, will be processed only in the following version.

Binary installation packages of these versions are uploaded on SourceForge.

At the time of their publication, the Alpha level of the next version should be available, in order to validate the upgrade and the upward and downward compatibility between versions. A new branch will be created for the sources.

Stable versions

After a sufficient period of test without important modifications, the last Release Candidate becomes stable.

You can use them for a real management. It remains useful to backup regularly your databases, especially if the version was released recently.

Binary installation packages of these versions are of course uploaded on SourceForge. They will be moved in "Old versions" folder after a new stable version is released, and will stay there as long as this site will allow it.

Release naming

Contents