<div dir="ltr">So, as I review this, we have a few different guidelines for maintainers and release processes. <div>We have ReadtheDocs [1], the old Community site [2] and the RTD documentation for releases [3] -- while 1 and 2 look nearly identical, 2 will eventually disappear so that we're not maintaining two active copies. </div><div>Should we be consolidating these new guidelines into a new page in RTD? </div><div><br></div><div>- amye </div><div><br></div><div>[1] <a href="https://gluster.readthedocs.io/en/latest/Contributors-Guide/Guidelines-For-Maintainers/">https://gluster.readthedocs.io/en/latest/Contributors-Guide/Guidelines-For-Maintainers/</a> </div><div>[2] <a href="http://www.gluster.org/community/documentation/index.php/Guidelines_For_Maintainers">http://www.gluster.org/community/documentation/index.php/Guidelines_For_Maintainers</a> </div><div>[3] <a href="https://gluster.readthedocs.io/en/latest/Contributors-Guide/GlusterFS-Release-process/">https://gluster.readthedocs.io/en/latest/Contributors-Guide/GlusterFS-Release-process/</a> </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 13, 2016 at 3:13 AM, FNU Raghavendra Manjunath <span dir="ltr"><<a href="mailto:rabhat@redhat.com" target="_blank">rabhat@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">+1.<div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Tue, May 10, 2016 at 2:58 AM, Kaushal M <span dir="ltr"><<a href="mailto:kshlmster@gmail.com" target="_blank">kshlmster@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div><div>On Tue, May 10, 2016 at 12:01 AM, Vijay Bellur <<a href="mailto:vbellur@redhat.com" target="_blank">vbellur@redhat.com</a>> wrote:<br>
> Hi All,<br>
><br>
> We are blocked on 3.7.12 owing to this proposal. Appreciate any<br>
> feedback on this!<br>
><br>
> Thanks,<br>
> Vijay<br>
><br>
> On Thu, Apr 28, 2016 at 11:58 PM, Vijay Bellur <<a href="mailto:vbellur@redhat.com" target="_blank">vbellur@redhat.com</a>> wrote:<br>
>> Hi All,<br>
>><br>
>> We have encountered a spate of regressions in recent 3.7.x releases. The<br>
>> 3.7.x maintainers are facing additional burdens to ensure functional,<br>
>> performance and upgrade correctness. I feel component maintainers should own<br>
>> these aspects of stability as we own the components and understand our<br>
>> components better than anybody else. In order to have more active<br>
>> participation from maintainers for every release going forward, I propose<br>
>> this process:<br>
>><br>
>> 1. All component maintainers will need to provide an explicit ack about the<br>
>> content and quality of their respective components before a release is<br>
>> tagged.<br>
>><br>
>> 2. A release will not be tagged if any component is not acked by a<br>
>> maintainer.<br>
>><br>
>> 3. Release managers will co-ordinate getting acks from maintainers and<br>
>> perform necessary housekeeping (closing bugs etc.).<br>
>><br>
>> This is not entirely new and a part of this process has been outlined in the<br>
>> Guidelines for Maintainers [1] document. I am inclined to enforce this<br>
>> process with more vigor to ensure that we do better on quality & stability.<br>
>><br>
>> Thoughts, questions and feedback about the process are very welcome!<br>
>><br>
<br>
</div></div>+1 from me. Spreading out the verification duties will help us do<br>
better releases.<br>
<span><br>
>> Thanks,<br>
>> Vijay<br>
>><br>
>> [1]<br>
>> <a href="http://www.gluster.org/community/documentation/index.php/Guidelines_For_Maintainers" rel="noreferrer" target="_blank">http://www.gluster.org/community/documentation/index.php/Guidelines_For_Maintainers</a><br>
>><br>
>><br>
> _______________________________________________<br>
> maintainers mailing list<br>
> <a href="mailto:maintainers@gluster.org" target="_blank">maintainers@gluster.org</a><br>
> <a href="http://www.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/maintainers</a><br>
</span>_______________________________________________<br></div></div>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
</blockquote></div><br></div>
<br>_______________________________________________<br>
maintainers mailing list<br>
<a href="mailto:maintainers@gluster.org">maintainers@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/maintainers</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">Amye Scavarda | <a href="mailto:amye@redhat.com" target="_blank">amye@redhat.com</a> | Gluster Community Lead</div></div>
</div>