Allow DB migration backports to Juno
Registered by
Dan Smith
Just as we did at the beginning of the Juno dev cycle, we need to reserve a range of DB migrations as the first DB change in Kilo. This will allow a range to be used for migration backports to Juno if needed.
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Reserve 10 migrations for backports
Gerrit topic: https:/
Addressed by: https:/
Add project_id+deleted index to backport position
(?)