Versioning strategy

The Simplicité platform is available on 3 branches:

Each version is identified with a major version number (e.g. 5 or 4.0) and a patch level number (e.g. P20).

The patch level number is suffixed:

Note : as of version 5 the "official" full version number is noted 5.p.r where p is the patch level number (e.g. 3 for P03) and r is an incremental number increased each time a revision is pushed on the release branch. On the prerelease branch r is always 0-beta and on the master branch r is always 0-alpha.

The functional changes (e.g. new features, refactored features, etc.) are only done on the master branch.

Fixes are applied on all branches:

The usual delay between two release versions is between 3 and 6 months. In the meantime the released version is amended by critical fixes.

Note: the prerelease branch is only used before a release to come. It corresponds first to a beta version then to a release candidate version. After the release and before the next release candidate phase it just contains the same version as the release version.

Long term maintenance

Some of the stable versions become long term maintenance versions.

This means a new maintenance branch is forked from the release and the major version number is then increased. This maintenance branch is named x.y-maintenance (where x.y being the forked major version number, e.g. 3.2).

A maintenance branch only receives critical fixes.

The following major versions have a maintenance branch:

Maintenance branch Long term maintenance end date
4.0 release notes January 15th, 2024
3.2 release notes Expired
3.1 release notes Expired
3.0 release notes Expired
2.x Expired

Note: The long term maintenance end date of a given version is defined as date of the fork of the next maintenance branch plus 3 years. After this end date the maintenance branch does not receive any fix.