Migration Toolkit for Applications and Migration Toolkit for Runtimes
Life Cycles and Support Policies
Red Hat provides support and maintenance over stated time periods for the major versions of the Migration Toolkit products (MTA and MTR). The published life cycle calendars for the Migration Toolkits allow customers and partners to effectively plan, deploy, and support Red Hat Application Services products.
The life cycle associated with Migration Toolkit 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.
Software updates for the Migration Toolkits, if and when available, are delivered via updated Operators for the OpenShift Container Platform (in the case of MTA) or downloadable software patches on the Customer Portal (in the case of MTA).
NOTE: Defect and security fixes are only provided for the latest Migration Toolkit release, therefore upgrading to the latest release is required in order to receive the current updates. Additionally, upgrades and patches are expected to be applied to a supported configuration as published.
The life cycle for a major release of Migration Toolkit product is divided into two primary phases: the Full Support Phase, and the Maintenance Support Phase. The Migration Toolkits do not have Extended Life Support (ELS) or Extended Update Support (EUS) support phases.
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 or as required for qualified security patches.
Phase 2: Maintenance Support
Start Date: in the of the Migration Toolkits, the Maintenance Support phase begins as soon as a new version of the given Toolkit is released. For example, MTR 2.0 moves into the Maintenance Support phase as soon as the MTR 3.0 release is made.
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.
The following table details each type of software maintenance performed during a typical life cycle:
|Description||Full Support||Maintenance Support|
|Unlimited-incident technical support1||Yes||Yes|
|Access to Product Knowledgebase||Yes||Yes|
|Access to Product Downloads||Yes||Yes|
|Access to Product Discussions||Yes||Yes|
|Access to Support, Configuration and Troubleshooting Tools||Yes||Yes|
|Asynchronous Security Patches4||Yes||Yes|
|Asynchronous Bug-Fix Patches2||Yes||Yes|
|New Certifications (JVMs, DBs, etc.)||Yes||No|
- Full details of support services are provided as part of the Subscription Agreement.
- 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.
- Major and Minor releases are the primary source for software enhancements. Rollups, updates, and patches are specifically reserved for bug fixes.
- Latest security update information available at: access.redhat.com/site/security/updates/.
Listed below are the life cycle dates for all currently supported Red Hat Application Services 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.