Open Stack

On 2014-10-09 09:54:17 +0200 (+0200), Christian Berendt wrote:
> Because the Python 2.6 support should be dropped I think it makes sense
> to change all existing Python 2.6 jobs to non-voting.

We can't switch it to non-voting because we're still required to
enforce these jobs on stable/icehouse and stable/juno for their
support lifetimes (likely around a year from now) and also on all
libraries and clients used with the Juno integrated release for the
same duration.

What we ought to do is remove gate-{name}-python26 from the
python-jobs template in layout.yaml and instead, add the jobs
explicitly to the check and gate pipelines of projects where we need
to continue supporting it and set specific branch filters on each of
those jobs corresponding to the support requirements (e.g. limit
them to stable/icehouse and stable/juno for servers but not limit
them for clients/libraries which have only master branches).

And as Andreas points out in his reply, we shouldn't press forward
with this until after Juno is officially out the door next week.
-- 
Jeremy Stanley