[Gluster-Maintainers] Master branch lock down for stabilization (unlocking the same)

Pranith Kumar Karampuri pkarampu at redhat.com
Tue Aug 14 04:51:51 UTC 2018

On Mon, Aug 13, 2018 at 10:55 PM Shyam Ranganathan <srangana at redhat.com>

> On 08/13/2018 02:20 AM, Pranith Kumar Karampuri wrote:
> >     - At the end of 2 weeks, reassess master and nightly test status, and
> >     see if we need another drive towards stabilizing master by locking
> down
> >     the same and focusing only on test and code stability around the
> same.
> >
> >
> > When will there be a discussion about coming up with guidelines to
> > prevent lock down in future?
> A thread for the same is started in the maintainers list.

Could you point me to the thread please? I am only finding a thread with
subject "Lock down period merge process"

> > I think it is better to lock-down specific components by removing commit
> > access for the respective owners for those components when a test in a
> > particular component starts to fail.
> Also I suggest we move this to the maintainers thread, to keep the noise
> levels across lists in check.
> Thanks,
> Shyam

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/maintainers/attachments/20180814/2ebfebd6/attachment.html>

More information about the maintainers mailing list