[MGNLCTS-136] Choose appropriate deprecation strategy for Content Translation Support Created: 01/Apr/21  Updated: 23/Aug/22

Status: Open
Project: Content Translation Support
Component/s: None
Affects Version/s: 2.5.2
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Sang Ngo Huu Assignee: Sang Ngo Huu
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 3.75d
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: Migrate Content Translation Support
Team: AuthorX

 Description   

Currently, CTS module already has compatibility module. There are 2 options:

  • Move compatibility code to compatibility module magnolia-content-translation-support-compatibility as well then add new implementation to core magnolia-content-translation, consider to remove code in compatibility module
  • Create new core module magnolia-content-translation-core then moving the core code + M6 code to this module

After discussion, we can learn from dam module:

  • Remove "old" compatibility
  • Provide new one magnolia-content-translation-compatibility

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