[CONTEDIT-230] Verify that content-editor & stories app are fully migrated Created: 18/May/20  Updated: 27/May/21  Resolved: 27/May/21

Status: Closed
Project: Content Editor
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Jorge Franco Assignee: Dai Ha
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to CONTEDIT-363 Release Stories App v2 Closed
Template:
Acceptance criteria:
[X]* Contend Editor dependencies: should not depend on vaadin v7 and magnolia ui compatibility
[X]* Ensure ui-test passed
[X]* Verify content editor v1 and v2 in the same webapp with updated widgetset-pro
[X]* List of PRs by orders: ui, content-editor, widgetset-pro, demo-project, dx-core, npm-cli
[X]* Scan for migration test problems
Task DoR:
Empty
Date of First Response:
Epic Link: Stories App Migration
Sprint: Content Mngmt 03, Content Mngmt 04
Story Points: 8

 Description   

Release

  • v2 to master
  • v1 to branch

6.2.x will bundle v1 with flexibility to move to v2 if customer wants it
6.3 will bundle v2 with flexibility to downgrade to v1

Outcome: a wiki page to preview the release plan before process CONTENTEDIT-363

 



 Comments   
Comment by Jorge Franco [ 26/May/20 ]

AC:

  • Check that all labels are in internationalization properties files, not in yaml
  • Check that there are not compatibility dependencies used
  • Check that produced jcr stories are the same than old ones
  • Check that no Vaadin 7 imports are present in the code
  • Check no deprecations are present in the code
  • Show the app to product(Simon)
Comment by Jorge Franco [ 08/Feb/21 ]

From other ui applications migrated experience:

Comment by Dai Ha [ 27/May/21 ]

Ta

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