[MGNLSITE-49] Specify the move to new registry API and YamlConfigurationSource for sites in more detail and identify possible sub tasks Created: 28/Jan/16 Updated: 04/Apr/16 Resolved: 19/Feb/16 |
|
| Status: | Closed |
| Project: | Magnolia Site Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0.x |
| Type: | Task | Priority: | Neutral |
| Reporter: | Michael Mühlebach | Assignee: | Philip Mundt |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 1.5d | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Account: | |||||||||
| Epic Link: | Light Development 1.0 | ||||||||
| Sprint: | Basel 31 | ||||||||
| Story Points: | 5 | ||||||||
| Description |
|
Identify the scope and impact of moving to new registry API and YamlConfigurationSource (a.k.a Sites via YAML) for sites. We should have separate issues that cover all steps of the task. Topics that need to be addressed:
|