Add mitaka release milestone for db migrations
Bug #1559318 reported by
Abhishek Raut
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| vmware-nsx |
Fix Released
|
Undecided
|
Abhishek Raut | ||
Bug Description
We do this for every release.
Add a 'mitaka' tag to the end of the alembic contract and expand branches in vmware-nsx repo.
| Changed in vmware-nsx: | |
| assignee: | nobody → Abhishek Raut (abhraut) |
| Changed in vmware-nsx: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to vmware-nsx (master) | #1 |
| Changed in vmware-nsx: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to vmware-nsx (stable/mitaka) | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to vmware-nsx (stable/mitaka) | #3 |
| tags: | added: in-stable-mitaka |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit e2971f49f03aa61
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:
neutron-
where <milestone> is an alias for all the revisions for a
milestone.
Closes-Bug: #1559318
Change-Id: Ie1324f8f998e1d