The CloudBees CloudBees CD/RO release strategy is detailed below.
|CloudBees plans to increase the velocity of long-term support (LTS) releases to enable our customers to deploy new CloudBees CD/RO capabilities into production environments at a faster pace.|
For critical security vulnerabilities, CloudBees aims to release patches as soon as possible.
The traditional “big” release is an LTS release. LTS releases are for
Major.Minor versions (for example, 11.0 LTS, 11.1 LTS, etc.), supported for a maximum of 12 months, and identified by the LTS suffix. Minor versions are typically released every 3-4 months. This timeframe can be extended as necessary, to ensure customers always have access to four actively-supported LTS releases.
MRs typically contain defect fixes, patches for high and medium security vulnerabilities, and do not contain DB schema changes. MRs are for
Major.Minor.Maintenance versions (for example, 11.0.1, 11.0.2, etc.) and released approximately every month or less, as needed. MR releases are supported as long as their parent LTS
Major.Minor version is actively supported.
|Fixes for high and medium security vulnerabilities will be included in the next maintenance release, as appropriate.|
HRs are released on an as-needed basis to address specific customer situations, such as critical defects that can cause production outages, critical security issues, or issues that have a severe negative impact on customers. For critical security vulnerabilities, CloudBees aims to release a hotfix patch as soon as possible. HRs follow the
Major.Minor.Hotfix version number convention (for example, 10.2.3, 11.0.3, etc.) and can be made available on any supported LTS release or MR, as needed. Typically, the next MR or LTS release will absorb these changes to allow customers to move past the HR by upgrading to a later version.