Takashi Yamamoto <yamam...@midokura.com> wrote: > hi, > > On Wed, Mar 9, 2016 at 9:01 PM, Henry Gessau <hen...@gessau.net> wrote: >> Takashi Yamamoto <yamam...@midokura.com> 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 any issues, and >> the patch is independent of the milestone tagging. >> >> Please let me know if I am missing the issue(s). > > [1] is depending on patches which actually fixes mismatches. [2] [3]
Thanks. Gerrit's UI strikes again. > [2] https://review.openstack.org/#/c/287014/ > [3] https://review.openstack.org/#/c/287015/ > >> >>> >>> [1] https://review.openstack.org/#/c/287016/ >>> >>> On Tue, Mar 8, 2016 at 11:52 PM, Henry Gessau <hen...@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 >>>> >>>> __________________________________________________________________________ >>>> OpenStack Development Mailing List (not for usage questions) >>>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> __________________________________________________________________________ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
