Red Hat CodeReady Studio Life Cycle and Support Policy

Red Hat CodeReady Studio will be sunset on April 19, 2022. The corresponding community project ('JBoss Tools') is the succeeding toolkit.

Overview

Red Hat provides a published product life cycle for Red Hat CodeReady Studio (“CodeReady Studio”), in order for customers and partners to effectively setup their development infrastructure. The life cycle for a major or minor release of Red Hat CodeReady Studio 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 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 Studio to the most current supported version.

Phase 2: Maintenance Support Phase

During the maintenance phase, qualified security patches of Critical or Important impact, as well as select mission-critical bug-fix patches may be delivered, if and when available.

The release cadence changed from the annual major releases to the quarterly minor releases, which is reflected in the lifecycle dates. In most cases the updates 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.)

Supported Software

Upgrade Policy

Red Hat CodeReady Studio 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 Studio 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.