Maintenance Release Vehicle Definitions

• Scheduled release
• Supports upgrade paths for specific versions, which is defined in the release notes

• Version numbers for major releases increase based on the formula X+1.Y.Z. 
• Version numbers for minor releases increase based on the formula X.Y+1.Z

Where X is the primary version number, Y is the secondary version number, and Z the patch number.

• New features
• Improvements
• Bug fixes

• Release notes are available on the documentation portal
• Documentation on features, improvements, and bug fixes are available on the documentation portal

• Delivered as a standalone product installer
• Available from Licensing Website and Managed Services Licensing Website
• May require content repository migration

• Scheduled release
• Currently, cannot be rolled back

• Patch release number is a single digit number
• After installation, will increase the installed release number patch digit, based on the formula X.Y.Z.SPx
• Where X is the primary version number, Y is the secondary version number, and Z the patch number. x is the service pack number..

• Improvements
• Bug fixes
• Common Interest feature packs (if any)

• Release notes available on the documentation portal
• Documentation on features, improvements, bug fixes on the documentation portal

• Delivered as a package
• Available on Package Share
• Requires existing functional installation

• All fixes QA validated
• Overall package sanity with automation runs

• Single delivery model of releasing fixes
• Aggregator content package containing content package of individual components
• CFPs are rollover of hot fixes and no improvements are part of it.

X.Y.Z.CFPx

Where X is the primary version number, Y is the secondary version number, and Z the patch number. x is the cumulative service pack number.

CFP is cumulative fix pack containing fixes of all components through specified dates. For example, if a customer applies CFP3, then CFP3 = CFP1 + CFP2.

• Delivered as a package
• Available on Package Share
• Dependent on the latest service pack released
• CFP is self-dependant. Customers need not worry about finding/resolving dependencies. CFP should be installed on latest released Service Pack.
• CFP can be installed as a single package, which improves customer experience.

• Similar to a standard CFP, but only contains Oak related fixes
• COFP is self-dependant (no dependencies). Customers need not worry about finding/resolving dependencies. [1]

As necessary

• The COFP installation process has been simplified to improve customer experience. (Customers can just install a single package for all components).

QA validated

Package that includes one or more files created to solve a product defect that significantly degrades essential services or significantly impacts business operations. 

On an exception basis, for the following issues when the CFP vehicle is not applicable:

• An error in the software prevents the production use of the software.
• An error in the software causes system instability. 
• An error in the software causes data corruption or data loss.

• Delivered as a package
• Available on Package Share
• Dependent on the latest service pack released
• Most hot fixes are stand-alone, unless specified. Can be installed in any order. Can be verified through the Package Share Details tab of the Dependencies element.

• Validated by Customer Care
• AEM hot fixes do not benefit from the same level of quality assurance as service packs or product releases. Therefore, they should first be validated on a staging environment as part of the quality deployment processes.

• Delivered as package by AEM Customer Care
• Not necessarily included in service packs or full releases

• Contains product enhancements, scheduled for a subsequent product release, but delivered early based on the decision of Adobe's Product Management.
• Features are always merged with the next major release and then backported to the AEM version required by the customer
• Common Interest and GA feature packs are merged into the next service pack

• New features
• Improvements
• Bug fixes (incremental product updates)

• Delivered as a package
• Available on Package Share. Customers accept Adobe's Terms and Conditions through Package Share.