Experience Manager update release vehicle definitions update-release-vehicle-definitions
This document includes details about the various types of ÃÛ¶¹ÊÓƵ Experience Manager releases, including full releases, feature packs, and services packs that ÃÛ¶¹ÊÓƵ delivers to its customers.
NOTE
For release schedule of Experience Manager update releases, refer to Experience Manager update releases roadmap
Full Release full-release
Items
Description
Definition
- Scheduled release
- Supports upgrade paths for specific versions that are 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 service-pack
Item
Description
Definition
- Scheduled release
- Currently, it 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
- New features
- Improvements
- Bug fixes
- Common Interest feature packs (if any)
Documentation
- Release notes are 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 Software Distribution
- Requires existing functional installation
Level of Testing
- All fixes QA validated
- Overall package sanity with automation runs
Cumulative Fix Pack cumulative-fix-pack-aem
Item
Description
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.
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 a 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 are available on the documentation portal
Cadence
Quarterly
Availability and Installation
- 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 the 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
Overlay overlay
Item
Details
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 Experience Manager Customer Care
- Not necessarily included in service packs or full releases
Level of Testing
Validated by Customer Care
Feature Pack feature-pack
Items
Details
Definition
- Feature Packs are add-on functionalities and are delivered through a service packs. If an Experience Manager version has released its last service pack, ÃÛ¶¹ÊÓƵ will not deliver any feature pack for it in the future.
- FPs contain product enhancements, scheduled for a subsequent product release, but delivered early based on the decision of ÃÛ¶¹ÊÓƵ’s Product Management.
- Features are always merged with the next major release. They are then ported to the Experience Manager version required by the customer
- Common Interest and GA feature packs are merged into the next service pack
Naming
cq-<Release Version>-featurepack-<feature pack ID>-<feature pack version>Inclusions
- New features
- Improvements
- Bug fixes (incremental product updates)
Documentation
Documentation is available on adobe.com.
Cadence
Varies with Product area
Availability and Installation
- Delivered via Service Packs
- Available on Software Distribution. Customers accept ÃÛ¶¹ÊÓƵ’s Terms and Conditions through Software Distribution.
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 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 of 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.
recommendation-more-help
79ddcbae-8d7c-448f-ba97-83d1381a2e12