Versions Compared

Old Version 118

changes.mady.by.user Viet Nguyen

Saved on

compared with

New Version 119

changes.mady.by.user Martin Drápela

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: de-RGB + polish why we go ... box

...

  1. Stop the application server.
  2. Extract the new Magnolia bundle.
  3. Replace JAR files in the WEB-INF/lib folder of your old Magnolia instances with new JARs from the bundle.
  4. Remove any module JARs you had previously removed from your instances. Add any modules you might have added.
  5. Optional: Delete all indexes to give them a little boost. Delete the index folder under each workspace directory: repositories/magnolia/workspaces/<workspace>/index. Indexes are recreated on startup, which might take a while depending on the size of your repository.
  6. If you customized magnolia.properties files, compare the changes to the file in the new bundle. Properties may have been added and removed.
  7. Read release notes for all intermediary versions for any additional update tasks.
  8. Restart the application server.
  9. Using your browser, go to the Magnolia instances and run the Web update.

Recommendations

  1. Update to your latest minor release version first before upgrade to recent major release. A May 2017 example: a customer was considering an upgrade from 5.4.1 to 5.5.4 (latest release at that time). The correct sequence would have been: 5.4.1 → 5.4.12 → 5.5.4 instead of  5.4.1 → 5.5 → 5.5.4 .

    Info

    Why we go that way?

    Because when a customer

    report

    reports issues when

    migration of

    migrating from 5.4.6 to 5.5, for instance, then we will support a

    work around

    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

    out dated

    an outdated technology stack (such as Java versions and security support from

    3rd

    third-party libraries), upgrade to 5.5.x, and the process repeats. So going with the latest release of each major release will free you from the issues and

    take advantage of

    bring you the improvements.

  2. Carefully look for "change" or "changes for ..." sections in the release notes since.
  3. 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.

...