Open Stack

On Fri, 14 Aug 2015, Robert Collins wrote:

> The vast majority of our developers do not fix such bugs. They react
> by blacklisting the proximate cause of the issue - the new release -
> locally, submit a patch to openstack/requirements *sometimes* and if
> we're really lucky file a bug upstream.

That sounds like a social disease.

> The constraints system proactively finds and highlights to anyone
> interested the same issues [presuming the issue can be shown in the
> gate]. It does that via a bot that updates constraints automatically
> via a periodic job.

I appreciate the value of the automation but from my standpoint in
addition to helping some aspects of the problem it also allows the
social disease to carry on. Maybe diseased is just the way things are
here, and if so, fine, we'll have to deal with it.

But I'm not going to stop popping my head up above the parapet every
now and again to say "hey, let's stop allowing this to be okay"
before going back to making more stuff.

> Its visible: follow
> https://review.openstack.org/#/q/status:open+project:openstack/requirements+branch:master+topic:openstack/requirements/constraints,n,z

Awesome, thanks for pointing this out, that will be useful.

But again: Underlying my assertion is that we don't _just_ need more
tools and automation we also need to remind ourselves of the kind of
environment that we're operating in, as humans.

I'm not against the automation of the gate side of things. Yes,
great, you and others are doing some stellar work to insure
stability. Thank you _very_ much. I'm arguing about the devstack
default.

And even then, I'm not arguing that we don't set it, rather that we
just pause a moment and think about the side effects, if any.

-- 
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent