[MAGNOLIA-4261] clean up version handlers of modules Created: 07/Feb/12  Updated: 22/Mar/12  Resolved: 16/Feb/12

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

Type: Task Priority: Major
Reporter: Daniel Lipp Assignee: Daniel Lipp
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-3962 Cleanup version handlers of modules Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MAGNOLIA-4271 further cleanup of CoreModuleVersionH... Sub-task Closed Daniel Lipp  
MAGNOLIA-4272 clean up version handler of enterpris... Sub-task Closed Daniel Lipp  
MAGNOLIA-4273 clean up versionhandler of Admininter... Sub-task Closed Daniel Lipp  
MAGNOLIA-4274 clean up version handler of mail module Sub-task Closed Daniel Lipp  
MAGNOLIA-4275 clean up versionhandler of cache module Sub-task Closed Daniel Lipp  
MAGNOLIA-4276 clean up version handler of templatin... Sub-task Closed Daniel Lipp  
MAGNOLIA-4277 clean up version handler of workflow ... Sub-task Closed Daniel Lipp  
MAGNOLIA-4278 clean up version handler of stk migra... Sub-task Closed Eric Hechinger  
MAGNOLIA-4279 clean up version handler of exchange-... Sub-task Closed Daniel Lipp  
MAGNOLIA-4280 clean up version handler of store-cli... Sub-task Closed Daniel Lipp  
MAGNOLIA-4281 clean up version handler of fckEditor... Sub-task Closed Daniel Lipp  
MAGNOLIA-4282 clean up version handler of DMS versi... Sub-task Closed Daniel Lipp  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

Since SCRUM-895/SCRUM-896 magnolia 4.4.6 is a prerequisite for update to 4.5 now, we can cleanup version handlers for all modules now.
Policy is to cleanup as soon as we touch them anyway.

For better traceability pls create a subtask to this ticket for every module.


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