Henry Gessau <HenryG at gessau.net> wrote: > By tomorrow we intend to tag the heads of all the neutron alembic branches > with the MITAKA label [1][2][3][4]. > > If you have a patch that adds an alembic migration and you want to get it > in > Mitaka you must be associated with a targeted BP/RFE/bug [5] and get your > code > merged by tomorrow (Wednesday, March 9). > > Here is a list of open reviews with DB migration changes [6]. Check if your > Mitaka-targeted patch is on the list and if so, reach out to me (HenryG) or > our PTL (armax) on IRC and let us know of your plans. > > -- HenryG > > [1] https://review.openstack.org/288212 > [2] https://review.openstack.org/288213 > [3] https://review.openstack.org/288214 > [4] https://review.openstack.org/288215 > [5] https://launchpad.net/neutron/+milestone/mitaka-rc1 > [6] > https://review.openstack.org/#/q/(project:openstack/neutron+OR+project:openstack/neutron-fwaas+OR+project:openstack/neutron-lbaas+OR+project:openstack/neutron-vpnaas)+status:open+file:%22%255E.*/versions/mitaka/.*%22+-label:workflow-1 > Note we are still in the middle of clarifying whether we want to allow DSCP feature in Mitaka, that involves alembic scripts. More details on the discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088717.html Thanks for holding the label patches. Ihar