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 |
|
I find the BootstrapEmptyRepositoriesTask and WebappBootstrap slightly confusing or misleading. I'm not sure if they're both completely correct. They might need better naming and/or documentation. (the whole bootstrap mechanism might need doc/tests too) |
| Comments |
| Comment by Vivian Steller [ 10/Dec/07 ] |
|
when doing this we also might want to fix this one: |
| Comment by Vivian Steller [ 10/Dec/07 ] |
|
Before fixing this we should cleanup "Bootstrap API" in general which is coverd by |
| 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. |