<p dir="ltr"></p>
<p dir="ltr">-Atin<br>
Sent from one plus one<br>
On 10-Jun-2016 6:09 PM, "Atin Mukherjee" <<a href="mailto:amukherj@redhat.com">amukherj@redhat.com</a>> wrote:<br>
><br>
><br>
><br>
> On 06/06/2016 10:00 AM, Vijay Bellur wrote:<br>
> > On Fri, Jun 3, 2016 at 10:36 AM, Vijay Bellur <<a href="mailto:vbellur@redhat.com">vbellur@redhat.com</a>> wrote:<br>
> >> On Fri, Jun 3, 2016 at 10:16 AM, Niels de Vos <<a href="mailto:ndevos@redhat.com">ndevos@redhat.com</a>> wrote:<br>
> >>> On Thu, Jun 02, 2016 at 10:55:58PM -0400, Vijay Bellur wrote:<br>
> >>>> On Sun, May 29, 2016 at 9:37 PM, Vijay Bellur <<a href="mailto:vbellur@redhat.com">vbellur@redhat.com</a>> wrote:<br>
> >>>>> Since we do not have any objections to this proposal, let us do the<br>
> >>>>> following for 3.7.12:<br>
> >>>>><br>
> >>>>> 1. Treat June 1st as the cut-off for patch acceptance in release-3.7.<br>
> >>>>> 2. I will tag 3.7.12rc1 on June 2nd.<br>
> >>>><br>
> >>>><br>
> >>>> Gentle reminder - I will be tagging 3.7.12rc1 in about 12 hours from<br>
> >>>> now. Please merge patches needed for 3.7.12 by then. Post that,<br>
> >>>> patches would be pushed out to 3.7.13.<br>
> >>><br>
> >>> I thought we didnt do the rc releases for the stable versions anymore?<br>
> >>> What is the reason for this change?<br>
> >>><br>
> >><br>
> >> This is for the convenience of maintainers to submit their feedback on<br>
> >> the release content. A tag is more convenient than a commit ID to<br>
> >> provide feedback and log bugs if necessary. Hence the change.<br>
> >><br>
> ><br>
> > I have tagged v3.7.12rc1.<br>
> ><br>
> > Maintainers - please use this tag to verify contents for your<br>
> > components and provide your feedback this week.<br>
> GlusterD sanity tests are executed. I've focused on cluster<br>
> expansion/shrink, volume management commands like create. start, stop,<br>
> delete along with expansion/shrink of a volume. volume set/get features<br>
> are also tested. Little bit of basic testing is done for tiering, quota.<br>
> Nothing abnormal found till now. So its a green from GlusterD team.</p>
<p dir="ltr">Along with that, I've also focused on testing the recent bug fixes done in the glusterd code space.</p>
<p dir="ltr">><br>
> ><br>
> > Thanks!<br>
> > Vijay<br>
> > _______________________________________________<br>
> > Gluster-devel mailing list<br>
> > <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> > <a href="http://www.gluster.org/mailman/listinfo/gluster-devel">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
> ><br>
> _______________________________________________<br>
> Gluster-devel mailing list<br>
> <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> <a href="http://www.gluster.org/mailman/listinfo/gluster-devel">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
</p>