Page History

...

1. Update to your latest minor release version first before upgrade to recent major release. A June 2018 example: a customer was is considering an upgrade from 5.5.8 to 5.7. The  The correct sequence would have beenbe: 5.5.8 → 5.5.10 → → 

   Artifact resource link
   rangeHigherVersion 5.6

   .6 → 5.7
   Info

   title	Why we go that way?

   Because when a customer reports issues when migrating from 5.4.6 to 5.5, for instance, then we will support a workaround/patch and later release the fix also in 5.4.7. The fix of the issue in 5.4.6 when migrating is usually located in version handlers. Then at some point, we drop 5.4.x because of an outdated technology stack (such as Java versions and security support from third-party libraries), upgrade to 5.5.x, and the process repeats. So going with the latest release of each major

   groupId info.magnolia.bundle artifactId magnolia-bundle-parent label $version renderType display_only resourceType POM

    → 

   Artifact resource link
   rangeHigherVersion 5.7 groupId info.magnolia.bundle artifactId magnolia-bundle-parent label $version renderType display_only resourceType POM

    → 5.7
   release will free you from the issues and bring you the improvements.

2. Update all external libraries required by the Magnolia release to which you intend to upgrade.
3. Carefully look for "change" or "changes for ..." sections in the release notes since.
4. Because the upgrade process takes time and is vulnerable to incidents, please minimize the risk by cleaning up your system, removing unused data, reindexing everything and doing a full backup first.

...