Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-2781

As a module developer, I can upgrade my content app in a clear and straight-forward way, so that I can experience a smooth migration to 5.3

    XMLWordPrintable

Details

    • Epic
    • Resolution: Fixed
    • Major
    • 5.3
    • None
    • content app
    • JCR-agnostic content apps migration

    Description

      Migration tasks should not do global config updates on content-apps but rather be run in each module. This is a cleaner approach since module devs have to change the bootstraps anyway.

      The goal is that each module takes care of itself, then we have a clear path for migration: e.g. add the following 3-4 UI tasks to your MVH and update your bootstrap files.

      This epic is about propagating these migration tasks to all affected modules, so that their content apps run smoothly on Magnolia 5.3.

      This also requires clear documentation on how to upgrade a module, including API changes, config/bootstrap updates, migration tasks to add to MVH.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                apchelintcev Aleksandr Pchelintcev
                mgeljic Mikaël Geljić
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: