Update mechanism improvements (MAGNOLIA-5529)

[MAGNOLIA-1666] updatemech : core could maybe register the default workspaces Created: 07/Aug/07  Updated: 04/Nov/15  Resolved: 04/Nov/15

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

Type: Sub-task Priority: Major
Reporter: Magnolia International Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-1602 Update mechanism Closed
relation
is related to MAGNOLIA-2300 ModuleManagerImpl.checkForUpdateOrIns... Closed
Template:
Date of First Response:

 Description   

For more flexibility, it might be interesting to have the core module register the default workspaces (user*, mgnl*, ...)
This could also lead to having the whole "website" management as a separate module.

(this probly won't happen for 3.1, but planning it there for now, just as a reminder)



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:29:08 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.