<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Mon, Aug 13, 2018 at 10:55 PM Shyam Ranganathan <<a href="mailto:srangana@redhat.com">srangana@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 08/13/2018 02:20 AM, Pranith Kumar Karampuri wrote:<br>
> - At the end of 2 weeks, reassess master and nightly test status, and<br>
> see if we need another drive towards stabilizing master by locking down<br>
> the same and focusing only on test and code stability around the same.<br>
> <br>
> <br>
> When will there be a discussion about coming up with guidelines to<br>
> prevent lock down in future?<br>
<br>
A thread for the same is started in the maintainers list.<br></blockquote><div><br></div><div>Could you point me to the thread please? I am only finding a thread with subject "<font size="2"><span style="font-weight:normal">Lock down period merge process"</span></font></div><div><font size="2"><span style="font-weight:normal"><br></span></font></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> <br>
> I think it is better to lock-down specific components by removing commit<br>
> access for the respective owners for those components when a test in a<br>
> particular component starts to fail.<br>
<br>
Also I suggest we move this to the maintainers thread, to keep the noise<br>
levels across lists in check.<br>
<br>
Thanks,<br>
Shyam<br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Pranith<br></div></div></div>