Red Hat CodeReady Workspaces Life Cycle and Support Policy
Overview
Red Hat provides a published product life cycle for Red Hat CodeReady Workspaces (“CodeReady Workspaces”), in order for customers and partners to effectively plan, deploy, and support their development infrastructure. The life cycle for a major or minor release of Red Hat CodeReady Workspaces is divided into two primary phases: the Full Support Phase and the Maintenance Support Phase.
During Phase 1 and Phase 2 (set below) of the life cycle, software covered by an active subscription receives support according to the Professional level Development support Service Level Agreement and Scope of Coverage.
Phase 1: Full Support Phase
During the Full Support Phase, qualified Critical and Important Security errata advisories (RHSAs), Urgent and Selected High Priority Bug Fix errata advisories (RHBAs) may be delivered as they become available, all other available fixes and qualified patches and Red Hat Enhancement Advisories (RHEAs) may be released via periodic quarterly releases.
Customers are expected to upgrade their CodeReady Workspaces to the most current supported version.
Phase 2: Maintenance Support Phase
During the maintenance phase, qualified security patches of Critical impact, as well as select mission-critical bug-fix patches, may be released, if and when available.
In most cases, these will be provided in a y-stream release, not a z-stream one. (For example, we’ll deliver a 1.1, not a 1.0.1.)
The following table details each type of software maintenance performed during a typical life cycle:
| Life-Cycle Phase | ||
|---|---|---|
| Description | Full Support | Maintenance Support |
|
Unlimited-incident technical support1 |
Yes | Yes |
| Asynchronous Security Patches | Yes | Yes |
|
Asynchronous Bug-Fix Patches2 |
Yes | Yes |
| Minor Releases | Yes | No |
| Software Enhancements |
Yes3 |
No |
1 Full details of support services are provided as part of the Subscription Agreement.
2 Red Hat can choose to address catastrophic issues with significant business impact for the customer through a hotfix, as a temporary measure while the bug-fix patch is being created.
3 Major releases are the primary source for software enhancements.
Supported Software
CodeReady Workspaces is reliant on the OpenShift support life cycle and is not supported beyond “Full Support” and “Maintenance Support” as noted in the OpenShift 3.x and OpenShift 4.x life cycles.
| Red Hat CodeReady Workspaces | ||||
|---|---|---|---|---|
| Version | GA | End of Full Support | End of Maintenance Support | OpenShift Versions Compatibility |
| 1.0 | Feb 5, 2019 | Apr 16, 2019 | July 16, 2019 | 3.11 - Supported |
| 1.1 | Apr 16, 2019 | Jun 5, 2019 | Sep 5, 2019 | 3.11 - Supported 4.0 - Unsupported, Development preview |
| 1.2 | June 5, 2019 | Nov 26, 2019 | Feb 26, 2020 | 3.11, 4.1 - Supported |
| 2.0 | Nov 26, 2019 | Until a subsequent release | 3 months after a subsequent release | 3.11, 4.1, 4.2 - Supported |
Details
CodeReady Workspaces provides developer features for different programming languages. Support for the Java and NodeJS stacks provided by Red Hat will be available through Red Hat Support channels and accessed through the Red Hat Customer Portal. Support for other languages and stacks will not be provided through Red Hat Support channels, but will be available through the open source community.
Upgrade Policy
CodeReady Workspaces gives the customer an ability to skip minor releases during upgrades. This means that traversing multiple minor versions to upgrade to the latest version is a supported path.
For example, if CodeReady Workspaces v1.3 is released and a customer is currently on v1.1, then a customer can directly upgrade from v1.1 to v1.3 without having to upgrade to v1.2 first.
In addition all existing workspaces/pods associated to a CodeReady Workspaces minor release are compatible with other minor releases. This compatibility is not guaranteed with upgrade to a next major release.