[MGNLCAMPU-88] Choose appropriate deprecation strategy for CAMPU Created: 07/Nov/20  Updated: 23/Aug/22

Status: Open
Project: Campaign Publisher
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Šimon Demočko Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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: Migrate campaign publisher to M6 UI
Team: AuthorX

 Description   

We'll need a compatibility module where we'll move old things and keep it bundled with the old pages app. 

  • Move old codebase to compatibility module
  • Hide old app
  • Deprecate classes..? Maybe unnecessary and expensive extra effort, since the whole module should be considered "deprecated" as it is a compatibility module. (possibly file ADR on the decision - outside of scope of this ticket)

Generated at Sun Feb 11 23:57:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.