このコンテンツは選択した言語では利用できません。
Chapter 1. Introduction
1.1. About Patches and Upgrades
Major Upgrades
A major upgrade or migration is required when an application is moved from one major release to another, for example, from JBoss EAP 6 to JBoss EAP 7. This type of migration is not addressed in this guide.
For instructions on how to migrate from previous releases of JBoss EAP, see the Migration Guide.
Minor Updates
JBoss EAP periodically provides point releases, which are minor updates that include bug fixes, security fixes, and new features. Minor updates are not applied via patching. If you plan to upgrade from one JBoss EAP point release to another, for example, from JBoss EAP 7.0 to JBoss EAP 7.1, code changes should not be required for applications that follow the Java EE specification and do not use any private, unsupported, or tech preview modules.
For instructions on how to upgrade from one JBoss EAP 7 point release to another, see the upgrading chapter.
Cumulative Patches
JBoss EAP also periodically provides individual or cumulative patches that contain bug and security fixes. Cumulative patches increment the minor release version by the last digit, for example from 7.0.1 to 7.0.2. These patches do not require migration and should not impact the server configuration files. The patch management system for ZIP/installer installations can also rollback the patch and server configuration.
For instructions on how to patch JBoss EAP, see the patching chapter.
1.2. Subscribing to JBoss Security Announcements
The JBoss team at Red Hat maintains a mailing list for security announcements for Red Hat JBoss Middleware products. You can subscribe to this mailing list to be notified of security-related announcements that affect JBoss EAP.
