WildFly Versioning: Difference between revisions
No edit summary |
No edit summary |
||
| (11 intermediate revisions by the same user not shown) | |||
| Line 12: | Line 12: | ||
The EAP/WildFly release stream contains ''major releases'' (EAP 6, EAP 7), ''point releases'' (EAP 6.4) and ''minor releases'' (EAP 6.4.4). | The EAP/WildFly release stream contains ''major releases'' (EAP 6, EAP 7), ''point releases'' (EAP 6.4) and ''minor releases'' (EAP 6.4.4). | ||
A ''major upgrade'' (or ''migration'') is required when moving from a major release to another. | |||
Point releases contain bug fixes, security fixes and new features. An ''[[EAP Upgrading|upgrade]]'' is required when moving between point releases. Code changes should not be required when updating to a new point release, provided that the application follows the JEE specifications and does not use private, unsupported or tech preview modules. Point releases may impact server configuration files. | |||
Minor releases are provided periodically to keep the installation up to date with bug and security fixes. They are provided as ''cumulative patches'' and they are applied via the ''CLI (or web console) [[EAP Patching|patching]] mechanism''. Patches should not impact the server configuration files. Security patches are provided by an ''erratum''. | |||
Latest revision as of 22:45, 15 March 2016
Internal
Relevance
- EAP 6.4
Overview
The EAP/WildFly release stream contains major releases (EAP 6, EAP 7), point releases (EAP 6.4) and minor releases (EAP 6.4.4).
A major upgrade (or migration) is required when moving from a major release to another.
Point releases contain bug fixes, security fixes and new features. An upgrade is required when moving between point releases. Code changes should not be required when updating to a new point release, provided that the application follows the JEE specifications and does not use private, unsupported or tech preview modules. Point releases may impact server configuration files.
Minor releases are provided periodically to keep the installation up to date with bug and security fixes. They are provided as cumulative patches and they are applied via the CLI (or web console) patching mechanism. Patches should not impact the server configuration files. Security patches are provided by an erratum.