Versions and releases
A version is just a milestone on the head branch made publicly available.
For each stable version, a maintenance branch is forked from the head branch (e.g.
On the head branch and on each maintenance branch, maintenance releases are regularly issued.
A version can be either in:
- Current maintenance phase, which means a weekly continuous delivery strategy is applied (for both functional changes and fixes).
- Active maintenance phase, which means a maintenance release is issued every 1 to 3 months (mainly for fixes but also for minor functional changes backported from current).
- Long term maintenance phase, which means the maintenance releases are issued every 3 months or more (for fixes only).
|Version||Maintenance phase||Maintenance end date|
|2.4, 2.5, 2.6.x, 2.7.0 and 3.0||n/a||Expired|
|3.1 release notes||Long term||December 2018|
|3.2 release notes||Long term||June 2020|
|4.0 release notes||Current||Not yet defined|
Note: The maintenance end date is be defined as date of the initial maintenance release of next version plus 3 years.