[MGNLLIC-70] Upgrade license system to handle next major version(s) Created: 13/Jul/18  Updated: 19/Oct/20  Resolved: 19/Oct/20

Status: Closed
Project: Magnolia License
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Epic Priority: Blocker
Reporter: Michael Mühlebach Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLLIC-69 New major version 6.x does not work w... Closed
Template:
Epic Name: 6.x license
Acceptance criteria:
Empty

 Description   

Goal

Make system around licensing ready for the next major version 6.x. This includes the license module, the license generator app used by sales, the online license module used by cloud solutions and potentially other places.

Acceptance criteria

  • The system must be able to read and create licenses for Magnolia 4, 5 and 6
  • The installation of the license generator to sales operatives (Dona, Vero, etc) has to be done as well
  • The capability to license of individual modules has to stay intact (although we don't use it today we want to do that in the near future)
  • All new code has to be tested by unit test thoroughly (meaning the coverage has to increase)
  • The system has to work with the cloud licensing system

Stretch goals

  • Ideally the refactoring allows and easy adaption when 7.x comes around
  • We want to have at some point the license module be part of any bundle (including ce) and refactoring should not make that harder. Ideally, if the code has to be restructured, it should become easier
  • We aim to have in the future a real licensing server and refactoring of the code shouldn't make that harder and if possible even easier

Open Question

  • General Version/License question: What licenses do we/sales want to distribute in the future? Should licenses be compatible with 5 & 6, should they be always separate or both (meaning individual licenses and an uber license for all versions). The answer should have no impact on the effort but will inform the solution.

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