[DOCU-1491] Improve upgrade to 5.6 process with practical tips Created: 25/Apr/18  Updated: 27/Jan/21  Resolved: 27/Jan/21

Status: Closed
Project: Documentation
Component/s: content
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Antti Hietala Assignee: Ashraf Khamis
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

User story:

We are currently are running 5.4.14 so we want to understand when is best to upgrade to maximise the improvements available. We also want to understand the needs to upgrade and any tips you have. – American Express

Improve the Upgrading to Magnolia 5.6 page with practical tips and lessons learned from client upgrades. bandersen and rgange have guided clients through the 5.4-to-5.6 process. Ask them to provide the content.

Acceptance criteria:

  • Upgrade instructions are realistic and set the right expectations.
  • Include lessons learned from actual upgrades.
  • Identify common pitfalls. 

Ideas:

  • Add "Lessons learned" info boxes in relevant places on the page.
  • Consider moving the upgrade page under 5.6 release notes. Current location under the Administration section is hard to find.


 Comments   
Comment by Richard Gange [ 25/Apr/18 ]

Some tickets related to my journey with Ancestry from 5.3.8 to 5.4.14 to 5.5.8:

  • SUPPORT-8445
  • SUPPORT-8291

Couple weird things that happened:

  • Going from 5.3.8 to 5.3.19 there was a custom classes (they had) where I needed to remove the @Inject annotation. Never quite understood why.
  • Making that jump from 5.4 to 5.5 can take hours not minutes, as our release notes claimed. We also had reports from other customer needing 4-5 hours to complete that part.
Comment by Martin Drápela [ 25/Apr/18 ]

We should probably be working on this ticket when doing DOCU-1458 - the upgrade page for 5.7.

Comment by Mercedes Iruela [ 26/Apr/18 ]

Some inputs from common issues in support:

  • I would add the list of modules that have been migrated to vaadin 8 and the version where it was done, as you know there were some issues in support related to it and magnolia instances were not able to start(MGNLUI-4295).
  • Same thing with Blossom module, where some bugs were found related to Magnolia 5.6: BLOSSOM-249 and BLOSSOM-247
  • Widgetset issue: SUPPORT-8559, that should have been fixed with ARCH-60.

 

Comment by Richard Gange [ 26/Apr/18 ]

Related to cloud but probably worth linking: https://wiki.magnolia-cms.com/display/MP/2018-04-10+Failed+upgrade+on+magnolia-cms.com

Comment by Richard Gange [ 26/Apr/18 ]

Also related is DOCU-1485. If you have a pom from an older project there could be some changes to be aware of. As far as dependency management. Bundle version vs project (platform) version.

Comment by Richard Gange [ 04/May/18 ]

Just finished a new tutorial on upgrading pom files.
https://wiki.magnolia-cms.com/display/WIKI/Updating+poms+from+older+projects

Comment by Richard Gange [ 14/May/18 ]

Here is another new page I created from my experience upgrading the training webapp from 5.5.7 to 5.6. https://wiki.magnolia-cms.com/display/DeveloperTraining55/%5BHidden%5D+training_workspace+update+to+5.6

Comment by Ashraf Khamis [ 27/Jan/21 ]

Closing the ticket as Obsolete after the 5.6 branch reached end of life in June 2020.

Generated at Mon Feb 12 01:18:35 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.