[openstack-dev] [all] Organizing a Gate Blocking Bug Fix Day

Jay Pipes jaypipes at gmail.com
Thu Jan 9 18:53:22 UTC 2014

On Thu, 2014-01-09 at 07:46 -0500, Sean Dague wrote:
> I think we are all agreed that the current state of Gate Resets isn't 
> good. Unfortunately some basic functionality is really not working 
> reliably, like being able to boot a guest to a point where you can ssh 
> into it.
> These are common bugs, but they aren't easy ones. We've had a few folks 
> digging deep on these, but we, as a community, are not keeping up with them.
> So I'd like to propose Gate Blocking Bug Fix day, to be Monday Jan 20th. 
> On that day I'd ask all core reviewers (and anyone else) on all projects 
> to set aside that day to *only* work on gate blocking bugs. We'd like to 
> quiet the queues to not include any other changes that day so that only 
> fixes related to gate blocking bugs would be in the system.
> This will have multiple goals:
>   #1 - fix some of the top issues
>   #2 - ensure we classify (ER fingerprint) and register everything we're 
> seeing in the gate fails
>   #3 - ensure all gate bugs are triaged appropriately
> I'm hopefully that if we can get everyone looking at this one a single 
> day, we can start to dislodge the log jam that exists.
> Specifically I'd like to get commitments from as many PTLs as possible 
> that they'll both directly participate in the day, as well as encourage 
> the rest of their project to do the same.

I'm in.

Due to what ttx mentioned about I-2, I think the 13th Jan or 27th Jan
Mondays would be better.

Personally, I think sooner is better. The severity of the disruption is
quite high, and action is needed ASAP.


More information about the OpenStack-dev mailing list