Re: [openstack-dev] [neutron] Last chance to finish changes affecting DB schema for Mitaka

2016-03-09 Thread Armando M.
On 9 March 2016 at 07:42, Ihar Hrachyshka wrote: > Henry Gessau 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

Re: [openstack-dev] [neutron] Last chance to finish changes affecting DB schema for Mitaka

2016-03-09 Thread Ihar Hrachyshka
Henry Gessau 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

Re: [openstack-dev] [neutron] Last chance to finish changes affecting DB schema for Mitaka

2016-03-09 Thread Henry Gessau
Takashi Yamamoto wrote: > hi, > > On Wed, Mar 9, 2016 at 9:01 PM, Henry Gessau wrote: >> Takashi Yamamoto wrote: >>> Henry, >>> >>> i think it's better to fix model vs migration mismatch issues [1] >>> before tagging. >>> how do

Re: [openstack-dev] [neutron] Last chance to finish changes affecting DB schema for Mitaka

2016-03-09 Thread Takashi Yamamoto
hi, On Wed, Mar 9, 2016 at 9:01 PM, Henry Gessau wrote: > Takashi Yamamoto wrote: >> Henry, >> >> i think it's better to fix model vs migration mismatch issues [1] >> before tagging. >> how do you think? > > I agree that [1] should be included in

Re: [openstack-dev] [neutron] Last chance to finish changes affecting DB schema for Mitaka

2016-03-09 Thread Henry Gessau
Takashi Yamamoto wrote: > Henry, > > i think it's better to fix model vs migration mismatch issues [1] > before tagging. > how do you think? I agree that [1] should be included in Mitaka, but it just adds the model-migration test to lbaas. The test passes so I don't see

Re: [openstack-dev] [neutron] Last chance to finish changes affecting DB schema for Mitaka

2016-03-08 Thread Takashi Yamamoto
Henry, i think it's better to fix model vs migration mismatch issues [1] before tagging. how do you think? [1] https://review.openstack.org/#/c/287016/ On Tue, Mar 8, 2016 at 11:52 PM, Henry Gessau wrote: > By tomorrow we intend to tag the heads of all the neutron alembic

[openstack-dev] [neutron] Last chance to finish changes affecting DB schema for Mitaka

2016-03-08 Thread Henry Gessau
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,