In one of the most recent CQ Gems ses­sions, Bertrand Delac­re­taz pre­sented the AEM 5.6 upgrade mech­a­nisms.

What if you wouldn’t be able to use the lat­est and great­est fea­tures of your great expe­ri­ence man­age­ment platform?

Com­pa­nies using Adobe AEM are keen to use the most recent release as it comes every year with great addi­tions that bring great value to them.

Adobe AEM is designed to make upgrades as nat­ural as pos­si­ble. And we lead by example!


Our main site dri­ves 2% of the global traf­fic and it is a crit­i­cal asset for the busi­ness of the company.

adobe​.com was upgraded to AEM 5.6 even before the release was announced.


This is the ref­er­ence web­site for AEM doc­u­men­ta­tion and many related tech­ni­cal sources.

dev​.day​.com is con­stantly upgraded to inter­me­di­ate inter­nal releases, and it hap­pens very early and very often in the devel­op­ment process.

For exam­ple: this site is cur­rently based on a build which was released inter­nally on May 24 2013: 7 days ago.

There are sev­eral rea­sons why this approach is of immense value for the prod­uct and for com­pa­nies adopt­ing it:

  1. Sta­bil­ity. Being able to upgrade an exist­ing site in par­al­lel with our inter­nal releases gives a lot of addi­tional indi­ca­tions on top of our stan­dard QE process.
  2. Back­ward com­pat­i­bil­ity of projects built on the AEM plat­form. dev​.day​.com (the web­site) was built on a pre­vi­ous release but still per­fectly runs on this lat­est build.
  3. Longevity test­ing. We want our soft­ware to pass the “at least 3 months on a real web­site” test even before any beta release.

This is a crit­i­cal aspect of the AEM suc­cess as a plat­form to sup­port com­pa­nies to man­ag­ing their cus­tomer expe­ri­ence, and to con­tin­u­ously deliver more and more value with every new release, adding new con­tent man­age­ment fea­tures, more sup­port for mul­ti­ple chan­nels, more inte­gra­tions with the other solu­tions of the Mar­ket­ing Cloud and much more.

By the way: this blog is hosted on the same plat­form as dev​.day​.com, so the page that you are cur­rently read­ing is deliv­ered by that May 24 2013 inter­nal build. Isnt’t that cool?