Update mechanism improvements
(MAGNOLIA-5529)
|
|
| 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: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Description |
|
Need to check how updating from 3.1-SNAPSHOT or 3.1-M2 to 3.1 ("final") behaves. Ideally, it should allow doing some updatings or checks... |
| Comments |
| Comment by Magnolia International [ 23/Oct/07 ] |
|
Handling classifiers ("-m3") will probably be left out for now; we should still somehow warn the user that the system won't be updated. |
| Comment by Magnolia International [ 03/Apr/08 ] |
|
We will definitely not handle snapshot versions for now - but when |
| 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. |