Maintenance Release Vehicle Definitions

You are reading the AEM 6.2 version of Maintenance Release Vehicle Definitions.
This documentation is also available for the following versions:  AEM 6.1 

This document includes details about the various types of Adobe Experience Manager (AEM) releases, including full releases, feature packs, and services packs that Adobe delivers to its customers.

Full Release

Definition
  • Scheduled release
  • Supports upgrade paths for specific versions, which is defined in the release notes
Naming
  • 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.

Inclusions
  • New features
  • Improvements
  • Bug fixes
Documentation
  • Release notes are available on the documentation portal
  • Documentation on features, improvements, and bug fixes are available on the documentation portal
Cadence Yearly
Availability and Installation
  • Delivered as a standalone product installer
  • Available from Licensing Website and Managed Services Licensing Website
  • May require content repository migration
Level of Testing Fully validated by QA

Service Pack

Definition
  • Scheduled release
  • Currently, cannot be rolled back
Naming
  • 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..
Inclusions
  • Improvements
  • Bug fixes
  • Common Interest feature packs (if any)
Documentation
  • Release notes available on the documentation portal
  • Documentation on features, improvements, bug fixes on the documentation portal
Cadence Quarterly
Availability and Installation
  • Delivered as a package
  • Available on Package Share
  • Requires existing functional installation
Level of Testing
  • All fixes QA validated
  • Overall package sanity with automation runs

Cumulative Fix Pack

Definition
  • 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.
Naming

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.

Inclusions

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

Documentation Release notes available on the documentation portal
Cadence Monthly
Availability and Installation
  • 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.
Level of Testing QA validated at Integration level and regression testing

Oak Cumulative Fix Pack

Definition
  • 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]
Naming oak <version>
Inclusions COFP is cumulative fix pack containing fixes of all Oak components for a specific 1.x version. For example, if the customer applies COHF 1.x.3, then COHF 1.x.3. = COHF 1.x.1 + COHF 1.x.2.
Documentation  
Cadence

As necessary

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

QA validated

Hot Fix

Definition

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

Naming cq-<Release Version>-hotfix-<hotfix ID>-<hotfix version>
Inclusions Includes fixes for a specific issue
Documentation Release notes of the public hotfixes are only available based on customer request through the AEM Support Portal.
Cadence As necessary
Availability and Installation
  • 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.
Level of Testing
  • 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.

Overlay

Definition  
Naming overlay-<ticket ID>
Inclusions Bug fix for a JS or JSP file
Documentation None
Cadence As necessary
Availability and Installation
  • Delivered as package by AEM Customer Care
  • Not necessarily included in service packs or full releases
Level of Testing Validated by Customer Care

Feature Pack

Definition
  • 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
Naming cq-<Release Version>-featurepack-<featurepack ID>-<featurepack version>
Inclusions
  • New features
  • Improvements
  • Bug fixes (incremental product updates)
Documentation Documentation is available on docs.adobe.com.
Cadence Varies with Product area
Availability and Installation
  • Delivered as a package
  • Available on Package Share. Customers accept Adobe's Terms and Conditions through Package Share.
Level of Testing General Availability feature packs are QA validated
  • [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 build 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 the same level of quality assurance as a cumulative fix pack, service pack, or product release. The final fix is delivered with the next COFP.

Any questions?

Have a question about this or any other AEM topic? Ask our Community.
Learn more about AEM topics on our help hub.
Was this helpful?

By submitting your feedback, you accept the Adobe Terms of Use.

Thank you for submitting your feedback.