Versionning strategy

A version is just a milestone on the main branch made publicly available.

For some particular major milestones a maintenance branch is forked from the main branch (e.g. 3.2 MAINTENANCE). The version number is increased after this maintenance branch is forked (e.g. after 3.2 MAINTENANCE was forked the main branch version became 4.0). On each maintenance branch, maintenance patches are regularly issued.


On the main branch, stable milestones are regularly made available: Pnn (e.g. 4.0 P22). The main branch is, in fact, split into 3 sub-branches: master (alpha), prerelease (beta) and release:


In production you must use only the release branch. The prerelease should only be used for testing/validation purposes. The master branch should not be used except for ponctual preview purposes.

Versionning timeline

A version can be either in:

Version Maintenance phase Maintenance end date
4.0 release notes Current Not yet defined
3.2 release notes Long term June 2020
3.1 release notes Long term December 2018
2.4, 2.5, 2.6.x, 2.7.0 and 3.0 n/a Expired

Note: The maintenance end date of a given version is be defined as date of the fork of the maintenance branch of next version plus 3 years.