<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 9, 2014 at 11:30 PM, Sean Dague <span dir="ltr"><<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Minor correction, we're going to do this on Jan 27th, to be after the i2 push, as I don't think there is time organize this prior.<br></blockquote><div><br></div><div>So FYI Jan 27th is a public holiday in Australia (Australia Day!), but given the timezone difference I think those of us in Australia can still participate on the 28th and it will still be the 27th in the US :-)<br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
It will also be a good way to start the i3 push by trying to get the gate back in shape so that we can actually land what people need to land for i3.<br>
<br>
-Sean<br>
<br>
On 01/09/2014 07:46 AM, Sean Dague wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think we are all agreed that the current state of Gate Resets isn't<br>
good. Unfortunately some basic functionality is really not working<br>
reliably, like being able to boot a guest to a point where you can ssh<br>
into it.<br>
<br>
These are common bugs, but they aren't easy ones. We've had a few folks<br>
digging deep on these, but we, as a community, are not keeping up with<br>
them.<br>
<br>
So I'd like to propose Gate Blocking Bug Fix day, to be Monday Jan 20th.<br>
On that day I'd ask all core reviewers (and anyone else) on all projects<br>
to set aside that day to *only* work on gate blocking bugs. We'd like to<br>
quiet the queues to not include any other changes that day so that only<br>
fixes related to gate blocking bugs would be in the system.<br>
<br>
This will have multiple goals:<br>
#1 - fix some of the top issues<br>
#2 - ensure we classify (ER fingerprint) and register everything we're<br>
seeing in the gate fails<br>
#3 - ensure all gate bugs are triaged appropriately<br>
<br>
I'm hopefully that if we can get everyone looking at this one a single<br>
day, we can start to dislodge the log jam that exists.<br>
<br>
Specifically I'd like to get commitments from as many PTLs as possible<br>
that they'll both directly participate in the day, as well as encourage<br>
the rest of their project to do the same.<br>
<br>
-Sean<br>
<br><span class="HOEnZb"><font color="#888888">
</font></span></blockquote><span class="HOEnZb"><font color="#888888">
<br>
<br>
-- <br>
Sean Dague<br>
Samsung Research America<br>
<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a> / <a href="mailto:sean.dague@samsung.com" target="_blank">sean.dague@samsung.com</a><br>
<a href="http://dague.net" target="_blank">http://dague.net</a><br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</font></span></blockquote></div><br></div></div>