Murano versioning
Murano is a complex system that comprises from a number of services and
technologies including several domain specific/markup languages. All of them
evolve and change from release to release. New futures are introduced, code is
being refactored and not always remains compatible with previous release.
But applications written for previous Murano versions must still work on newer
releases otherwise all applications would require at least retesting and often
code changes on each release.
Blueprint information
- Status:
- Complete
- Approver:
- Serg Melikyan
- Priority:
- High
- Drafter:
- Stan Lagun
- Direction:
- Approved
- Assignee:
- Stan Lagun
- Definition:
- Approved
- Series goal:
- Accepted for liberty
- Implementation:
- Implemented
- Milestone target:
- 1.0.1
- Started by
- Stan Lagun
- Completed by
- Serg Melikyan
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Improve the checks of Dynamic UI format versions
Addressed by: https:/
Improve the docs on UI Definitions format versions
Addressed by: https:/
Adds version info to ApplicationPackage
Addressed by: https:/
{WiP} Support for multi-versioned packages
Addressed by: https:/
{WiP} Version-aware YAML loading
Addressed by: https:/
{WiP} Context versioning
Addressed by: https:/
Restores back plugin support
Addressed by: https:/
Apply yaql conventions to __init__ parameters
Addressed by: https:/
Glance MuranoPackage Artifact
Addressed by: https:/
Added the support of Glance Artifact Repository