Red Hat SummitPrivate Automation Hub life cycle
Maintenance and Updates Statement for Automation Hub
Abstract
Making open source more inclusive
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.
Chapter 1. Overview
As part of an {PlatformName} subscription, customers have access to a supported version of {HubName}. Red Hat provides a published product life cycle for {HubName} so that customers and partners can properly plan, deploy, support, and maintain their {PrivateHubName}s that they use with the {PlatformNameShort}. This life cycle encompasses stated time periods for each version of {HubName}, starting with 4.2. The life cycle for each version of {HubName} is split into production phases, each identifying the various levels of maintenance over a period of time from the initial release date. While multiple versions of {HubName} will be supported at any one time, note that this life cycle applies to each specific version of {HubName} (4.2, 4.3 and so on).
Customers are expected to upgrade their {HubName} environments to the most current supported version of the product in a timely fashion. Bug fixes and feature-work will target only the latest versions of the product, though some allowance may be given for high security risk items.
Glossary
- Maintenance - Security and Application Bug fixes.
- Updates - Application Feature Enhancements
- Private Automation Hub - Refers to the customer installable {HubName} as provided via Subscription Manager.
Chapter 2. Life cycle dates
| Red Hat Automation Hub Release | General Availability | Full support ends | Maintenance Support 1 ends | End of Life |
|---|---|---|---|---|
| 4.4 | December 2, 2021 | June 2, 2022 | December 2, 2022 | June 2, 2023 |
| 4.2 | November, 18, 2020 | May 17, 2021 | November 18, 2021 | November 18, 2022 |
Chapter 3. Scope of coverage
Support will be provided for use according to the published Scope of Coverage in Appendix 1 of the Red Hat Enterprise Agreement. To encourage the rapid adoption of new technologies while keeping the high standard of stability inherent in Red Hat enterprise product, the product life cycle for Red Hat {HubName} is divided into three phases of maintenance, described below.
Chapter 4. Production phases
Full Support Phase
During the Full Support Phase, Red Hat will provide:
- Qualified critical and important security fixes
- Urgent and high priority bug fixes
- Select enhanced software functionality
This will be delivered in the form of sub-minor releases. A release of {HubName} is supported under the Full Support Phase for 6 months after its initial release.
Maintenance Support 1 Phase
During the Maintenance Support 1 Phase, Red Hat will provide:
- Qualified critical security fixes
- Urgent bug fixes
These fixes will be delivered in the form of sub-minor releases.
A release of {HubName} is supported under the Maintenance Support 1 Phase for 6 months after it leaves the Full Support Phase.
Maintenance Support 2 Phase
During the Maintenance Support 2 Phase, Red Hat will provide:
- Qualified critical security fixes
These fixes will be delivered in the form of sub-minor releases.
A release of {HubName} is supported under the Maintenance Support 2 Phase for 6 months after it leaves the Maintenance Support 1 Phase. All updates are provided at Red Hat’s discretion.
