The project plans to produce the following types of releases:
This LTS release cycle has the following goals:
Release versioning conforms to the semantic versioning 2.0.0 standard where by the major release is increment when a backwards-incompatible change is introduced. The following are examples of backwards-incompatible changes that would trigger an increment of the major release position:
Therefore, CloudStack users can expect that a family of major CloudStack releases is based on the same major Java/MySQL versions, maintain API compatibility, and supports for infrastructure components only expands. The project's release numbering differs slightly from Semantic Versioning as follows:
Finally, branch management and PR approval for regular and LTS releases processes follow those outlined in the CloudStack Release Principles topic. Due to their confidential nature of CVE mitigation, patches must be reviewed privately and cannot be submitted as PRs. Therefore, the security team reviews these patches privately – tracking the two (2) required LGTMs on the security@ mailing list.
The section outlines the process through which each release type of produced by the community.
.LTS branches are supported for a total of 18 months in the following manner:
The following are the types of changes that are permitted and guarantees provided to users:
Defect fixes that originate in an LTS branch will be forward merged to the supported regular release and master branches.
When a CVE is identified, the security team requires a private, expedited release process to address the issue. Users also need a release that is constrained to fixing only the CVE to minimize upgrade risk and downtime. Therefore, when a security release is required, the security team will review the proposed patch privately with a minimum of two (2) LGTMs required per our release principles. The patch will be forward merged to every impacted regular and LTS release currently supported – incrementing the security patch number. The security team will then create a release candidate for each security release and vote on each release candidate according to the community's bylaws. Security issues should be reported to email@example.com
|4.9.0||Regular||25 July 2016|
|15 December 2016||1 July 2018|
|22.214.171.124||LTS||6 January 2017||1 July 2018|
|126.96.36.199||LTS||11 September 2017||1 July 2018|
|188.8.131.52||LTS||12 February 2018||1 July 2019|
|184.108.40.206||LTS||2 July 2018|
|220.127.116.11||LTS||26 November 2018|
|18.104.22.168||LTS||13 Jul 2019|
|22.214.171.124||Regular||4 April 2019|
|126.96.36.199||LTS||24 September 2019||1 May 2021|
|188.8.131.52||LTS||2 May 2020||1 May 2021|
|184.108.40.206||LTS||26 May 2020||1 Jan 2022|
|220.127.116.11||LTS||3 March 2020||1 Jan 2022|
|18.104.22.168||LTS||19 Jan 2021||1 July 2022|