On Fri, 19 Oct 2018, Zane Bitter wrote:
Just to make it easier to visualise, here is an example for how the Zuul
config _might_ look now if we had adopted this proposal during Rocky:
https://review.openstack.org/611947
And instead of having a project-wide goal in Stein to add
`openstack-python36-jobs` to the list that currently includes
`openstack-python35-jobs` in each project's Zuul config[1], we'd have had a
goal to change `openstack-python3-rocky-jobs` to
`openstack-python3-stein-jobs` in each project's Zuul config.
I like this, because it involves conscious actions, awareness and
self-testing by each project to move forward to a thing with a
reasonable name (the cycle name).
I don't think we should call that "churn". "Intention" might be a
better word.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent tw: @anticdent
__________________________________________________________________________
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
