Hi Sachi and all,
I was recently looking into how stable/liberty branches are set for neutron
in terms of requirements caps, and I realized that we don’t have neither
version caps nor upper constraints applied to unit test jobs in
stable/liberty gate. We have -constraints targets defined in tox.ini, but
they are not running in gate.
I believe this situation leaves us open to breakages by any random library
releases out there. Am I right? If so, I would like to close the breakage
vector for projects I care (all neutron stadium).
I suggest we do the following:
- unless there is some specific reason for that, stop running unconstrained
jobs in neutron/master;
- enable voting for constraints jobs in neutron/liberty; once proved to
work fine, stop running unconstrained jobs in neutron/liberty;
- for neutron-*aas, introduce constraints targets in tox.ini, enable jobs
in gate; make them vote there/remove old jobs;
- after that, backport constraints targets to stable/liberty; make them
vote there/remove old jobs.
Does the plan make sense?
Ihar
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
