[PAGES-729] Page App - remove dependency on UI-compatibility layer Created: 01/Aug/22  Updated: 23/Aug/22

Status: Open
Project: Magnolia pages module
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Dominik Maslanka Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
PAGES-730 Implementation Sub-task To Do  
PAGES-731 Review Sub-task To Do  
PAGES-732 Pre-Integration QA Sub-task To Do  
PAGES-733 QA Sub-task To Do  
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)
Epic Link: Remove old (vaadin7 compatibility) framework module
Team: AuthorX

 Description   

User Story: as a SaaS user, I want to be sure that I'm using the latest stable version of the app so that I don't want to use the app based on the old legacy framework. 

Description: 
Our goal for 6.3 is to altogether remove the old UI framework; i.e. we will migrate all bundled apps to the M6 UI and remove the compatibility layer. This is equally important for SaaS where we do not want to run the legacy UI at all.

We need to remove dependency to Pages app which is magnolia descriptor:

https://git.magnolia-cms.com/projects/MODULES/repos/pages/pull-requests/415/overview 

 

Removing this dependency will let us continue with complete removal the compatibility layer 


Generated at Mon Feb 12 06:21:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.