On 08/14/2018 12:51 AM, Pranith Kumar Karampuri wrote: > > > On Mon, Aug 13, 2018 at 10:55 PM Shyam Ranganathan <srangana@xxxxxxxxxx > <mailto:srangana@xxxxxxxxxx>> wrote: > > 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" That is the one I am talking about, where you already raised the above point (if I recollect right). > > > > > 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 > > > > -- > Pranith _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
