The Simplicité platform is available on 3 branches:
releasebranch which contains the current stable version of the platform.
prereleasebranch which contains a preview version or a release candidate version of what will be eventually pushed on the the
masterbranch which contains the current development version of the platform.
Each version is identified with a major version number (e.g.
4.0) and a patch level number (e.g.
The patch level number is suffixed:
a(for "Alpha") on the
- by eiher
b(for "Beta") or
c(for "release Candidate) on the
- no suffix on the
Note : as of version 5 the "official" full version number is noted
pis the patch level number (e.g.
ris an incremental number increased each time a revision is pushed on the
releasebranch. On the
0-betaand on the
The functional changes (e.g. new features, refactored features, etc.) are only done on the
Fixes are applied on all branches:
- Any fix on the
masterbranch (critical, major or minor)
- Major and critial fixes on the
prereleasebranch during release candidate phase
- Only critical fixes on the
The usual delay between two release versions is between 3 and 6 months. In the meantime the released version is amended by critical fixes.
- In production you must use only the
prereleasebranch should only be used for validation purposes of the future released version.
masterbranch should never be used except for very ponctual testing purposes.
prereleasebranch 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 being the forked major version number, e.g.
A maintenance branch only receives critical fixes.
The following major versions have a maintenance branch:
|Maintenance branch||Long term maintenance end date|
||January 15th, 2024|
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.