Previously when we had one repo with one alembic branch we would
create a milestone revision on that single branch. Now we have
multiple repos and expand/contract branches for each repo. So
now we tag the final revision on every branch when we make a
milestone release.
The database can be upgraded with the command:
neutron-db-manage upgrade <milestone>
where <milestone> is an alias for all the revisions for a
milestone.
Closes-Bug: #1559318
Change-Id: Ie1324f8f998e1d551fc0aa3e3bc5f6a51523365a
(cherry picked from commit e2971f49f03aa61f25febe6f7fc2d34a0b1f18f9)
Reviewed: https:/ /review. openstack. org/295135 /git.openstack. org/cgit/ openstack/ vmware- nsx/commit/ ?id=9050d100a54 d63136eb63982ac 2feab6189ffc08
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit 9050d100a54d631 36eb63982ac2fea b6189ffc08
Author: Abhishek Raut <email address hidden>
Date: Fri Feb 26 04:27:43 2016 -0800
Tag the alembic migration revisions for Mitaka
Previously when we had one repo with one alembic branch we would
create a milestone revision on that single branch. Now we have
multiple repos and expand/contract branches for each repo. So
now we tag the final revision on every branch when we make a
milestone release.
The database can be upgraded with the command: db-manage upgrade <milestone>
neutron-
where <milestone> is an alias for all the revisions for a
milestone.
Closes-Bug: #1559318 551fc0aa3e3bc5f 6a51523365a f25febe6f7fc2d3 4a0b1f18f9)
Change-Id: Ie1324f8f998e1d
(cherry picked from commit e2971f49f03aa61