Hi, > Wiadomość napisana przez Jeremy Stanley <fu...@yuggoth.org> w dniu > 06.11.2018, o godz. 22:25: > > On 2018-11-06 22:05:49 +0100 (+0100), Slawek Kaplonski wrote: > [...] >> also add jobs like "devstack-xenial" and "tempest-full-xenial" >> which projects can use still for some time if their job on Bionic >> would be broken now? > [...] > > That opens the door to piecemeal migration, which (as we similarly > saw during the Trusty to Xenial switch) will inevitably lead to > projects who no longer gate on Xenial being unable to integration > test against projects who don't yet support Bionic. At the same > time, projects which have switched to Bionic will start merging > changes which only work on Bionic without realizing it, so that > projects which test on Xenial can't use them. In short, you'll be > broken either way. On top of that, you can end up with projects that > don't get around to switching completely before release comes, and > then they're stuck having to manage a test platform transition on a > stable branch.
I understand Your point here but will option 2) from first email lead to the same issues then? > -- > Jeremy Stanley > __________________________________________________________________________ > 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 — Slawek Kaplonski Senior software engineer Red Hat __________________________________________________________________________ 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
