Open Stack

On Mon, Nov 25, 2019, at 5:38 AM, Paul Belanger wrote:
> On Mon, Nov 25, 2019 at 04:02:13PM +1100, Ian Wienand wrote:
> > Hello,
> > 
> > Today I force-merged [5] to avoid widespread gate breakage.  Because
> > the change is in zuul-jobs, we have a policy of annoucing
> > deprecations.  I've written the following but not sent it to
> > zuul-announce (per policy) yet, as I'm not 100% confident in the
> > explanation.
> > 
> > I'd appreciate it if, once proof-read, someone could send it out
> > (modified or otherwise).
> > 
> > Thanks,
> > 
> Greetings!
> 
> Rather then force merge, and potential break other zuul installs. What
> about a new feature flag, that was still enabled but have openstack base
> jobs disabled?  This would still allow older versions of setuptools to
> work I would guess?
> 

I think the ship has sailed and the change has already been force merged. That said setuptools isn't something that you can easily control versioning of. For example when you create a virtualenv the version of setuptools in the virtualenv is automatically updated to the latest version. For this reason I think the merge was the best course of action.

> That said, ansible Zuul is not affected as we currently fork
> configure-mirrors for our open puproses, I'll check now that we are also
> not affected.
>