Update Release Vehicle Definitions | Adobe Experience Manager (2024)

DocumentationAEM Release Information

• Topics:
• Release Information

CREATED FOR:

• Beginner
• Intermediate
• Experienced
• Leader
• Developer
• Admin
• User

For release schedule of Experience Manager update releases, refer to Experience Manager update releases roadmap

• Scheduled release
• Supports upgrade paths for specific versions which are 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.

• New features
• 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 Software Distribution
• 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.

• Delivered as a package
• Available on Software Distribution
• Dependent on the latest service pack released
• CFP is self-dependent. Customers do not need to 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.

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

• Feature Packs are add-on functionalities and are delivered via Service Packs. If an Experience Manager version has released its last service pack, Adobe will not deliver any feature pack for it in future.
• FPs contain 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 ported to the Experience Manager 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 via Service Packs
• Available on Software Distribution. Customers accept Adobe’s Terms and Conditions through Software Distribution.

• 1: Oak fixes are not delivered as individual hot fixes. However, they are included in the subsequent Cumulative Oak hot fix. If necessary, a diagnostic built on top of the latest COFP can be made available. The precondition is that the customer has the latest COFP running. Diagnostic builds only provide the same level quality assurance as a hot fix. Therefore, they don’t provide as much quality assurance as a cumulative fix pack, service pack, or product release. The final fix is delivered with the next CFP.