[MAGNOLIA-7715] Start removal of compatibility modules from webapps Created: 04/Feb/20  Updated: 23/Mar/20  Resolved: 19/Mar/20

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2

Type: Story Priority: Neutral
Reporter: Roman Kovařík Assignee: Federico Grilli
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MAGNOLIA-7739 Remove old pages app from webapps Closed
dependency
depends upon MGNLADVCACHE-105 Untie from personalization compatibil... Closed
depends upon MGNLDEMO-330 Untie travel demo from compatibility ... Closed
relation
is related to MGNLPN-462 Untie from personalization compatibil... Open
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Sprint: UI Framework 20, UI Framework 17, UI Framework 18, UI Framework 19
Story Points: 13

 Description   

The initial goal of this effort was to remove compatibility modules from webapps and re-adding those to test webapp for UI tests.
As we started to tackle the modules involved, we noticed some of them, most notably personalization, still need a compatibility module. Due to time constraints, this has been postponed for completion after 6.2 (see MAGNOLIA-7736)
This issue also comprises removal of pages-app-compatibility where possible. In that case too, a follow-up ticket was created (MAGNOLIA-7739)



 Comments   
Comment by Federico Grilli [ 05/Mar/20 ]

Personalization still requires a compatibility module see MGNLPN-462

Generated at Mon Feb 12 04:26:11 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.