The primary purpose of a maintenance release is to fix bugs in the software, so that components work as originally documented. New features are limited in number and highly constrained. A Java ES maintenance release cannot include major or minor component releases, only update and point-fix releases. A Java ES maintenance release has the following general characteristics:
The release cannot introduce significant interface changes, new dependencies, or incompatibilities with respect to Java ES components
The release allows for quick adoption
Upgrade to the release requires no reconfiguration or migration of component data
The release involves minimal impact or risk