Red Hat JBoss Middleware Product Update and Support Policy


Overview

All Red Hat Middleware products follow a similar support and maintenance life cycle with the exception of Open Liberty which is included in the Red Hat Runtimes entitlement. Open Liberty provides a Continuous Delivery life cycle that’s documented on the Open Liberty Support Life Cycle page, and the contents of this current page does not apply to Open Liberty.

Red Hat provides support and maintenance over stated time periods for the major versions of Red Hat JBoss Middleware products (i.e., versions 4.x, 5.x, or 6.x). The published life cycle calendars for Red Hat JBoss products allow customers and partners to effectively plan, deploy, and support Red Hat JBoss Middleware products.

The life cycle associated with a Red Hat JBoss product identifies the various levels of maintenance for each release of that product over a period of time from the initial release—or general availability (GA)—to the end of the maintenance phase. Red Hat JBoss product life cycles are generally three, five, or seven years in length, depending on the product. For certain Red Hat JBoss products (as described below), an optional add-on Extended Life Cycle Support (ELS) subscription may be purchased to extend the life cycle by three (3) additional years.

Software updates to Red Hat JBoss products, if and when available, are delivered via software patches. Patches can be released individually on an as-needed basis, aggregated as part of a Cumulative Patch (CP), or included in a minor release (e.g., version 5.1). Patches may contain security and/or bug fixes. Feature enhancements are generally introduced in minor and major releases—not as patches or in CPs. Red Hat's goal is to maintain compatibility across the full life cycle of a product family (e.g., EAP 5.x patches, EAP 5.x CPs, and EAP 5.x releases are in the same EAP 5 product family). Patches, CPs, and minor releases are tested and qualified against prior releases for a given product family. Red Hat will use commercially reasonable efforts to provide compatibility with the initial major release (e.g., 5.0). Where incompatibilities arise, they will be documented in the release notes or may be reported as bugs.

Red Hat JBoss Middleware life cycles are designed to reduce the level of change within each major release over time, increasing predictability and decreasing maintenance costs. Released patches, CPs, and minor releases will remain accessible to active subscribers for the entire life cycle of a product family. Red Hat publishes product life cycle calendars in an effort to provide as much transparency as possibly but may make exceptions from these policies if unforeseeable conflicts arise (such as the end-of-life (EOL) of a dependent component or platform) that are outside of Red Hat’s control.

Every major version of a Red Hat JBoss Middleware product is maintained and supported independently during its life cycle. For each major version of a product, patch updates, if and when available, will be issued serially and will be applicable incrementally to previously released patches and CPs. Minor releases will aggregate the contents of prior patches and CPs, and they may add additional new functionality. Subsequent patches and CPs will be based on and require the installation of minor updates that precede them. During the entire life cycle, Red Hat makes commercially reasonable efforts to maintain API-level compatibility across all minor releases and asynchronous patches (e.g., EAP 5.1 will maintain API-level compatibility with EAP 5.0, the parent of the EAP 5 family). Possible exceptions to this rule could include fixes introduced to address Critical impact security issues. Furthermore, major versions of Red Hat JBoss Middleware products endeavor to maintain significant backward-compatibility with previous versions (e.g., EAP 5.0 endeavors to maintain significant backward compatibility with EAP 4.x) to aid with the migration of applications from one major release to another.

Life Cycle Phases

The life cycle for a major release of Red Hat JBoss Middleware products is divided into three primary phases: the Full Support Phase, the Maintenance Phase, and the Extended Life Phase.

Phase 1: Full Support

Start Date: General Availability

Full support is provided according to the published Scope of Coverage and Service Level Agreement. Likewise, Development Support is provided according to the published Scope of Coverage and Service Level Agreement. All available and qualified patches will be applied via periodic product updates and CPs, or as required for qualified security patches.

Phase 2: Maintenance Support

Start Date: no less than one (1) year after General Availability.

Production support is provided according to the published Scope of Coverage and Service Level Agreement. Likewise, Development Support is provided according to the published Scope of Coverage and Service Level Agreement. During the maintenance phase, qualified security patches of Critical or Important impact, as well as select mission-critical bug-fix patches, will be released.

Phase 3: Extended Life Support

Extended Life support is provided according to the published Scope of Coverage and Service Level Agreement. Unlike our Full Support and Maintenance Support phases, this support phase requires an ELS subscription in addition to a supported product’s base subscription. The Middleware ELS subscriptions provide decreasing support and maintenance over time as described below.

ELS-1:

ELS-1 delivers Critical impact security fixes and selected urgent-priority bug fixes, if and when available. For ELS-1 subscribers, Red Hat will generally continue to proactively provide the Critical impact security fixes if and when available independent of customer requests. ELS-1 is generally available for 3 years following the end of Maintenance Support.

ELS-2:

ELS-2 support is offered after the end of the ELS-1. ELS-2 provides limited ongoing technical support to include: Advice and guidance for migrating to current product releases, problem evaluation and workarounds. Bug fixes, security fixes, hardware enablement or root-cause analysis (other than to determine possible workarounds) are not available during this phase, and support is limited to existing installations only.

The duration of ELS-2 support is scheduled for 3 years and may be extended on a product-by-product basis. Red Hat reserves the right to terminate the ongoing support in the ELS-2 for a particular product at any time beyond the initial 3 year period.

The following table details each type of software maintenance performed during a typical life cycle:

  Life-Cycle Phase
Description Full Support Maintenance Support ELS-1 ELS-2
Unlimited-incident technical support1 Yes Yes Yes Yes
Access to Product Knowledgebase Yes Yes Yes Yes
Access to Product Downloads Yes Yes Yes Yes
Access to Product Discussions Yes Yes Yes Yes
Access to Support, Configuration and Troubleshooting Tools Yes Yes Yes Yes
Asynchronous Security Patches4 Yes Yes Yes5 No
Asynchronous Bug-Fix Patches2 Yes Yes Yes5 No
Minor Releases Yes No No No
Software Enhancements Yes3 No No No
New Certifications (JVMs, DBs, etc.) Yes Yes No 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 and Minor releases are the primary source for software enhancements. Rollups, updates, and patches are specifically reserved for bug fixes.
  4. Latest security update information available at: access.redhat.com/site/security/updates/.
  5. Red Hat provides Critical impact security fixes and selected urgent-priority bug fixes, if and when available. Additionally, Red Hat will generally continue to proactively provide the Critical impact security fixes if and when available independent of customer requests.

Life Cycle Duration

Red Hat JBoss product life cycles are generally three, five, or seven years in length as described below.

Long-life Product Life Cycle

A Long-life Product Life Cycle of seven years is generally applied to foundation products, such at Red Hat JBoss Enterprise Application Platform. As depicted below, the seven-year cycle includes four years of Full Support and three years of Maintenance Support. Extensions beyond the seventh year (“Extended Life Support”) are available under a separate subscription, scope of coverage, and SLA.

Long-life Product Life Cycle
Phase 1 Full Support (4 years) Phase 2 Maintenance Support (3 years) Phase 3 Extended Life Support (3-6 years)
Year 1 Year 2 Year 3 Year 4 Year 5 Year 6 Year 7 Year 8 Year 9 Year 10 Year 11 Year 12 Year 13

Standard Product Life Cycle

A Standard Product Life Cycle of five years applies to most Red Hat JBoss products. The Standard Product Life Cycle is also composed of two phases, Full Support and Maintenance Support. Extensions beyond the fifth year (“Extended Life Support”) are available under a separate subscription, scope of coverage, and SLA.

Standard Product Life Cycle
Phase 1 Full Support (3 years) Phase 2 Maintenance Support (2 years) Phase 3 Extended Life Support (3-6 years)
Year 1 Year 2 Year 3 Year 4 Year 5 Year 6 Year 7 Year 8 Year 9 Year 10 Year 11

Limited Product Life Cycle

The Limited Product Life Cycle of three years is generally applied to newer product areas and rapidly changing technologies such as development frameworks. The Limited Product Life Cycle is only composed of one phase, the Full Support Phase, however, variations may include a Maintenance Phase for some product releases. Extensions beyond the third year (“Extended Life Support”) are available under a separate subscription, scope of coverage, and SLA.

Limited Product Life Cycle
Phase 1 Full Support (3 years) Phase 3 Extended Life Support (3-6 years)
Year 1 Year 2 Year 3 Year 4 Year 5 Year 6 Year 7 Year 8 Year 9

Product Life Cycle Dates

Listed below are the life cycle dates for all currently supported Red Hat JBoss Middleware products. Life cycle dates for product releases that have reached their end of support life can be found on the Archived JBoss Product Life Cycle Information page.

Red Hat JBoss Enterprise Application Platform

JBoss Enterprise Application Platform expansion pack (JBoss EAP XP or EAP XP)

JBoss Enterprise Application Platform expansion pack (JBoss EAP XP) is subject to a separate Support and Life Cycle Policy.
Please refer to the JBoss Enterprise Application Platform expansion pack (JBoss EAP XP or EAP XP) Life Cycle Policy page.

Red Hat Data Grid

Red Hat JBoss Web Server

Red Hat support for Spring Boot

Note: Spring Boot 2.2 support will end when the Spring Community upstream version 2.2 has reached End of Life.

Red Hat build of Node.js

Node.js support aligns with the Node.js LTS life cycle dates defined by the Node.js Release Working Group, generally consisting of 18 months of full support followed by 12 months of maintenance support.

Red Hat build of Thorntail

Red Hat build of Eclipse Vert.x

Red Hat build of Quarkus

Red Hat Fuse

Red Hat JBoss Fuse Service Works

Red Hat AMQ

Red Hat 3scale API Management Platform

Red Hat JBoss Data Virtualization

Red Hat Process Automation Manager (formerly Red Hat JBoss BPM Suite)

Note: Entando App Manager Included. Entando App Manager follows a 3 year life cycle. Entando App Manager 5.x full support from May 2018 to May 2020. Maintenance support from May 2020 to May 2021

Note: Support for containerization of product bits is discontinued for 6.x from ELS-1 onward. Please note health index grades are not maintained henceforth.

Red Hat Decision Manager (Formerly Red Hat JBoss BRMS)

Note: Support for containerization of product bits is discontinued for 6.x from ELS-1 onward. Please note health index grades are not maintained henceforth.

Red Hat JBoss SOA Platform

Note: SOA-P 5.X is also a supported version of any Fuse Service Works or Fuse Subscription. Published SOA-P Life Cycle policy provisions apply.

Red Hat Integration

  Full Support Maintenance Support
Family GA Life Cycle Start End Start End
Debezium 1.x Apr 2020 Limited Apr 2020 Apr 2022 N/A N/A
Service Registry 1.x July 2020 Limited July 2020 July 2022 N/A N/A

Red Hat JBoss Core Services Collection Lifecycle Dates

Listed below are the life cycle dates for all currently supported Red Hat JBoss Core Services Collection services. Life cycle dates for Core Service releases that have reached their end of support life can be found on the Archived JBoss Product Life Cycle Information page.

Red Hat Single Sign-On

Apache HTTP Server

Note: Only the latest update of 2.4.x version of the Red Hat JBoss Core Services HTTP server is maintained.

Red Hat JBoss Operations Network

Note: As of October 2015 JON is no longer sold as a separate offering. After October 2015, all Middleware subscription renewals will automatically include JON Management.

Note: Migration Support delivers Critical impact security fixes and selected urgent-priority bug fixes, if and when available. Red Hat will generally continue to proactively provide the Critical impact security fixes if and when available independent of customer requests.

Web Connectors

Family GA End of Full Support End of Maintenance Support
1.2.461 May 2016 May 2022 Nov 2022

Note: The most recent version of the latest major release of Web Connectors is supported.

Apache Jsvc

Family GA End of Full Support End of Maintenance Support
1.1.01 May 2016 May 2022 Nov 2022

Note: The most recent version of the latest major release of Apache Jsvc is supported.

Products that are not listed above are either no longer actively sold or have reached the end of their supported Life Cycle. For more information check the Archived JBoss Product Life Cycle Information page.