[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 Created: 31/Mar/14 Updated: 30/Mar/15 Resolved: 09/Apr/14 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | content app |
| Affects Version/s: | None |
| Fix Version/s: | 5.3 |
| Type: | Epic | Priority: | Major |
| Reporter: | Mikaël Geljić | Assignee: | Aleksandr Pchelintcev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | migration | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Epic Name: | JCR-agnostic content apps migration | ||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Date of First Response: | |||||||||||||
| 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. |
| Comments |
| Comment by Magnolia International [ 03/Apr/14 ] |
|
Ideally, a single task with a very good name |
| Comment by Aleksandr Pchelintcev [ 03/Apr/14 ] |
|
The list of modules affected:
|