-
New Feature
-
Resolution: Fixed
-
Major
-
None
-
None
-
-
Empty show more show less
We had some brainstorming sessions today about the update mechanism that will be part of Magnolia 3.1.
We put our ideas down in mindmaps. While that format might not be ideal to read for someone who did not participate in the meetings, we also see it as a good compromise between ease of creation, maintenance and usefulness, as opposed to long-ish spec-ish text documents. We'll be happy to provide info or clarify points that are not clear by themselves, and/or discuss any of them.
The first one is an attempt to list all the problems to solve and features we'd like to see in there:
http://www.mind42.com/pub/mindmap?mid=fd256f03-1679-4b9a-a788-b768bb2b2a04
The seconds focuses more on technical or practical aspects, with some decisions being taken or viewpoints being adopted:
http://www.mind42.com/pub/mindmap?mid=8f526afb-f339-4884-9a47-f9207e80704b
- depends upon
-
MAGNOLIA-1209 Module dependencies should be able to handle version numbers in a more flexible way
- Closed
-
MAGNOLIA-1285 modules: dependency check should get impoved (flexible version mappings)
- Closed
- is depended upon by
-
MAGNOLIA-1663 Updatemech : observation should be "paused"
- Closed
-
MAGNOLIA-1664 updatemech : certains tasks can be optional
- Closed
-
MAGNOLIA-1666 updatemech : core could maybe register the default workspaces
- Closed
-
MAGNOLIA-1670 Updatemech : review exception handling (loading and lifecycle)
- Closed
-
MAGNOLIA-1448 update: lists configuration updates to perform during update
- Closed
-
MAGNOLIA-1400 Update mechanism : when updating from 3.0.x, remove metadata on expression nodes
- Closed
-
MAGNOLIA-1638 magnolia-exchange-simple should be a module
- Closed
-
MAGNOLIA-1662 Wrap modules' servlets in Filters
- Closed
-
MAGNOLIA-1672 Updatemech : extract from MagnoliaMainFilter
- Closed
-
MAGNOLIA-1678 Update of filter configuration
- Closed
-
MAGNOLIA-1665 updatemech : module version stored in repo is not consistent
- Closed
-
MAGNOLIA-1667 Updatemech : the whole process should be running in a separate thread
- Closed
-
MAGNOLIA-1668 Updatemech : new filters configuration
- Closed
- is related to
-
MAGNOLIA-1633 Move editor, developer and securitymanager users to the samples module
- Closed
-
MAGNOLIA-1659 always register repositories, nodetypes and workspaces from module definitions
- Closed
-
MAGNOLIA-850 replace the usage of betwixt
- Closed