Red Hat Developer Hub Life Cycle

Overview

Red Hat provides a published product life cycle for Red Hat Developer Hub (RHDH), in order for customers and partners to effectively plan their development infrastructure. The life cycle for a major or minor release of Red Hat Developer Hub is divided into two primary phases: the Full Support Phase and the Maintenance Support Phase.

Red Hat aims to forecast releases at a 3 month cadence, providing customers ample opportunity to plan. Each release will be supported for a total of about six months by combining the Full and Maintenance Support cycles. During these phases (see details below) of the life cycle, software covered by an active subscription receives support according to Red Hat's Production Support Terms of Service and Scope of Coverage.

Full Support Phase

This phase begins with the GA of a minor version and ends with the superseding minor release; a time period of about three months.

During the Full Support Phase, qualified Critical and Important Security Advisories (RHSAs) and Urgent and Selected High Priority Bug Fix Advisories (RHBAs) will be released as they become available; all other available fix and qualified patches may be released via periodic updates. In order to receive security and bug fixes, customers are expected to upgrade Developer Hub to the most current supported micro (1.x.y) version.

Maintenance Support Phase

This phase commences at the end of the Full Support phase and ends when the 2nd superseding minor version is released; resulting in a Maintenance phase period of approximately three months.

During the Maintenance Support phase, qualified Critical and Important Security Advisories (RHSAs) and Urgent and Selected High Priority Bug Fix Advisories (RHBAs) will be released as they become available. Other Bug Fix (and Enhancement (RHEA) Advisories may be released at Red Hat’s discretion, but should not be expected.

At the end of the maintenance support phase, the respective release of Red Hat Developer Hub will be considered End of Life. Red Hat will make commercially reasonable efforts for software and documentation to remain available to customers for a given major (eg. v1) release; however no technical support will be provided. Full functionality of Red Hat Developer Hub may require access to hosted services provided by Red Hat, the availability of these services cannot be guaranteed for unmaintained and unsupported versions of Red Hat Developer Hub.

Life Cycle Dates

Supported Platforms

Red Hat Developer Hub Platform
1.0
  • OpenShift Container Platform 4.12, 4.13, 4.14
  • [Dev Preview] Amazon Elastic Kubernetes Service (Amazon EKS)
  • [Dev Preview] Microsoft Azure Kubernetes Service (Microsoft AKS)
  • [Dev Preview] Google Kubernetes Engine (Google GKE)
1.1
  • OpenShift Container Platform 4.12, 4.13, 4.14, 4.15
  • Red Hat OpenShift Service on AWS (ROSA)
  • Azure Red Hat OpenShift (ARO)
  • Amazon Elastic Kubernetes Service (Amazon EKS)
  • Microsoft Azure Kubernetes Service (Microsoft AKS)
  • [Dev Preview] Google Kubernetes Engine (Google GKE)

Footnotes

  1. Red Hat can choose to address critical or important bug fixes upon request, with significant business impact for the customer through a hot fix, as a temporary measure while the bug fix patch is being created.
  2. The latest Major and Minor releases are the primary source for software enhancements. Roll-ups, updates, and patches are specifically reserved for bug fixes.
  3. Latest security update information available at: https://access.redhat.com/support/offerings/production/soc/
  4. Red Hat provides Critical impact security fixes and selected urgent-priority bug fixes, if and when available.
  5. Scope of coverage available at: https://access.redhat.com/support/offerings/techpreview
  6. Service level agreements available at: https://access.redhat.com/third-party-software-support
  7. For a list of supported plugins, see the Dynamic plugins support matrix in the product release notes: https://access.redhat.com/documentation/en-us/red_hat_developer_hub