CloudBees Accelerator Release Strategy update

Original Creation Date: 2019-08-30 00:52:46 UTC

We are excited to announce an update to the Accelerator release strategy. We realize that some customers like to take advantage of newer features at an accelerated pace, so we are introducing a new release type called ‘Preview Release’(PR). These preview releases allow us to deliver additional capabilities to our customers at a faster pace. Customers get early access to upcoming product innovations enabling them to test functionality and to provide feedback which can be incorporated in a subsequent release. Though these are produced in shorter cycles, they are production quality which customers could put into production if shorter upgrade cycles are something they are comfortable with. Customers should, of course, install these into test environments to try out the new features and provide feedback. Customers will need to be nimble and upgrade to the next PR in order to pick up defect fixes. Unlike traditional releases, PR don’t have maintenance releases. Defect fixes will be available by upgrading to the subsequent PR. 

With the addition of this new release type, we will now have 4 distinct types of release outlined below.

1. Long Term Support (LTS) Release

The traditional “big” release that we have been doing are now called LTS Release. New LTS Releases are Major or Major.Minor (e.g. 11.0 LTS, 11.1 LTS) versions, typically released every 6 months. An LTS Release is identified by the LTS suffix. An LTS release is supported for a minimum of 18 months. This timeframe will be extended as necessary to ensure that customers always have access to two actively supported LTS Releases.

2. Maintenance Release (MR)

New MR versions are Major.Minor.Maintenance (e.g. 11.0.1, 11.0.2) versions, released approximately every 3 months or sooner if needed. MR releases are supported as long as their parent LTS Major.Minor version is actively supported (e.g. 11.0). An MR release typically contains defect fixes, and does not contain DB schema changes. In some cases, we might expedite an MR release.

3. Hotfix Release (HR)

Hotfix Releases are released on an as-needed basis to address specific customer situations. Hotfixes are typically issued to address critical defects, which can cause production outages, security issues or have a severe negative impact to customers. They can be made available on any supported LTS or MR as needed.  Typically, the next MR or LTS release will absorb these changes so a customer can move past the hotfix release by upgrading to a later version.

4. Preview Releases (PR)

New PR versions are date based (e.g. 2019.08 PR, 2019.09 PR) versions, released roughly every 1-2 months. This rapid schedule allows us to deliver new features at a faster pace. PR will not receive MR releases (maintenance releases) or hotfixes. Instead, defect fixes and features will be made available in a subsequent PR release. All new features introduced in PR releases will get rolled into the subsequent LTS release. A customer who is on a PR is expected to upgrade to the next LTS release. Hence for customers where typical upgrade cycles are once or twice a year, it is recommended to use LTS in production environment and use PR in a test environment to provide feedback on new features.