CloudIta Releases
Timeline
| Abel LTS | |
| First release | December 2016 |
| Estimated retirement | May 2018 |
| Actual retirement |
| Development Testing | Abel LTS | |
| December 2016 | 0.0.1 |
Understanding the release cycle
The development release cycle is two to four weeks long. Each cycle freezes the master development branch and applies integration and upgrade tests for the duration of one cycle before it is released and the next release's code is frozen for testing. Once released, there is no effort to backport fixes; developer focus in on the next development release which is usually only a few weeks away.
There are three to four stable releases a year. Each stable release will receive a name (e.g., 'Jewel') and bug fix backports at least until the next stable release is out.
Every other stable releases is a LTS (Long Term Stable) and will receive updates until two LTS are published. * Long Term Stable : until the next two LTS are published * Stable release : until the next stable release is published * Development / testing release : no backports
For each stable release:
- Integration and upgrade tests are run on a regular basis and their results analyzed by CloudIta developers.
- Issues fixed in the development branch (master) are scheduled to be backported.
- When an issue found in the stable release is reported, it is triaged by CloudIta developers.
- The stable releases and backport team
publishes
point releasesincluding fixes that have been backported to the stable release.
In the timeline, the life time of a LTS is calculated to be approximately 18 months after the month of the first release.
Release numbers conventions
The versioning scheme is as follows:
- x.0.z - development releases (for early testers and the brave at heart)
- x.1.z - release candidates (for test clusters, brave users)
- x.2.z - stable/bugfix releases (for users)