[MGNLEE-815] We shouldn't have to release two content-editor versions at the same time Created: 21/Sep/23  Updated: 30/Oct/23

Status: Open
Project: Magnolia DX Core
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0

Type: Task Priority: Neutral
Reporter: Maxime Michel Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to BUILD-1179 Introduce a safety net step that make... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: 6.3 Consolidation
Team: Foundation

 Description   
  • this is a corner case that the bot doesn't support, even goes against Maven principles, requiring manual involvement
  • dx-core bundles content-editor v1 and then the demo showcases content-editor v2. hence, we could rollback the content-editor v2 back to v1 when 6.3 comes out
  • that way releasing both branches is easy, 6.2 keeps its relevant maintenance v1 version and 6.3 can showcase content-editor v2

Background

Why have we shipped two different versions of content-editor so far?

6.2 still ships with content-editor v1 by default (in dx-core-webapp), because upgrading to v2 is not directly compatible (change of data structure, hence required changes in project templates), only the demo-webapp bumps it to v2

Problems

  • 6.2.40's release included a SNAPSHOT version of content-editor v2 because content-editor v1 had been released by hand and since v2 version is not managed in root pom, it is out of the bot's reach. This problem could easily have been avoided by releasing v2 manually instead, but given we don't do such releases frequently, this is hard to remember. Also, the release process shouldn't require manual steps.
  • In 6.2.27, Maxime & Federico tried to allow the bot to manage both versions, in the end this resulted in broken customer setups. The reason isn't 100% clear but customers got their content-editor v1 version upgraded to v2. See:
  • because of the pecularities with the setup, and adding to the complexity of the situation, we have to have a dedicated VersionMatcher for content-editor (info.magnolia.mgmt.service.preflight.ThreeWayVersionMatcher.ContentEditorThreeWayMatcher)

Generated at Mon Feb 12 05:33:32 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.