db-archiving spec missing developer impact
Bug #1427402 reported by
Walt Boring
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Ivan Kolodyazhny |
Bug Description
The kilo db-archiving cinder spec currently has "None" for the developer impact. This is definitely not the case. When shadow tables are part of cinder, any developer making db changes also has to make shadow table changes.
We need to update the spec to talk about the scenarios of changes required for developers adding new tables, modifying existing tables and migrating data.
The spec in question:
https:/
Changed in cinder: | |
milestone: | none → kilo-3 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | kilo-3 → 2015.1.0 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/160534
Review: https:/