AuthorTopic: Some news in development organisation (Read 17341 times)

As it has been planned for a long time, the development management has changed. This change solves the problem with a complicated work on multiple versions at the same time. Also release creation has been simplified a lot, which will lead to more frequent releases.

The project has migrated from SVN to Git. There are 3 main branches (versions) at the moment: 0.57, 0.58 and the master. The master is always the most up-to-date code, it's the code for the upcoming 0.59 version.

New releases will be created far more often. Nightly builds have been abandoned and will not be released anymore. A new beta release will be created if there's something to test.

A beta release is, as the name says, a testing release. There are known issues and the version is not always stable.

For bigger changes, a whole new version will be created (e.g., last is 0.58 now, next will be 0.59). For versions which look more promising or which are very much liked by the community, there will probably be more beta releases.

If there is one version, where the last beta release has became stable enough, a release candidate (RC) version will be released. If the RC version is stable, it will be marked as a final stable version.