[MTE-124] Introduce MTK2 with M6 dialogs Created: 14/Jan/20 Updated: 21/Dec/21 Resolved: 07/Jun/21 |
|
| Status: | Closed |
| Project: | Magnolia Templating Essentials |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.0 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Roman Kovařík |
| Resolution: | Done | Votes: | 0 |
| Labels: | VN-Testing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 4h 10m | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||||||
| Epic Link: | Migrate MTK to new framework | ||||||||||||||||||||||||||||||||||||
| Sprint: | UI FW 29 | ||||||||||||||||||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||||||||||||||||||
| Description |
|
Update MTK dialogs to M6
|
| Comments |
| Comment by Simon Lutz [ 27/Feb/20 ] |
|
For now: make sure conversion/compatibility works well rather than going for the actual update. Update to happen later. |
| Comment by Šimon Demočko [ 04/Feb/21 ] |
|
Hi czimmermann. We're wondering:
|
| Comment by Christopher Zimmermann [ 04/Feb/21 ] |
|
Great question. I have removed that explicit approach from the ticket description. Idea: Does anything speak against just changing the definitions and creating a new major version of the MTE, (1.6 or 2.0) - and then each project can choose which version of MTE/MTK they want to use? But then how to handle bundling? To not introduce a breaking change in a minor version, I guess we still have to bundle MTE 1.5 series with 6.2 series and then update to new dialogs in MTE 1.6/2.0 only with Magnolia 6.3. (However, in the demo bundle we could already switch to the MTE 1.6/2.0 I would think.) Or could we introduce the changes on the 6.2 series and just advise customers if they want to keep using MTE 1.5 for compatibility reasons they can just use that in their own custom bundle? |
| Comment by Roman Kovařík [ 04/Feb/21 ] |
I think those are the reason we haven't do this approach with other modules and we did always created compatibility modules with the old config and keeping the old module name.
Update: |
| Comment by Roman Kovařík [ 26/May/21 ] |
Demo webapp is using mtk2 templates (e.g. mtk2:pages/basic).
|