Reserve database migrations for stable/icehouse backports
Registered by
Dolph Mathews
on 2014-01-30
Following the lead of Nova, keystone should "reserve" several migrations numbers in the master branch at the beginning of the Juno cycle for the purpose of backporting database migrations to stable/icehouse if necessary. This should remain true as long as we're using sqlalchemy-migrate instead of alembic.
On two occasions, keystone has sorely needed this functionality (most recently, https:/
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Low
- Drafter:
- Dolph Mathews
- Direction:
- Needs approval
- Assignee:
- Dolph Mathews
- Definition:
- New
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
-
2014.2
- Started by
- Dolph Mathews on 2014-01-30
- Completed by
- Dolph Mathews on 2014-06-04
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add placeholders for reserved migrations
(?)
