<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 10, 2017 at 6:21 PM, Niels de Vos <span dir="ltr"><<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Fri, Nov 10, 2017 at 11:23:51AM +0530, Jiffin Tony Thottan wrote:<br>
> Hi,<br>
><br>
</span><span class="">> I am planning to do 3.12.3 release today 10:00 pm IST (4:30 pm GMT).<br>
><br>
> Following bugs is removed from tracker list<br>
><br>
> Bug 1501235 - [SNAPSHOT] Unable to mount a snapshot on client -- based on<br>
> discussion on gerrit, it can be target for 3.13<br>
> instead of the 3.12.x release<br>
><br>
> Bug 1507006 - Read-only option is ignored and volume mounted in r/w mode --<br>
> assigned to none, no progress in master bug as well,<br>
<br>
</span>It is suspected that it already has been fixed in current releases.<br>
We'll need to write a test-case for it and have it merged in master<br>
(+backports). It is not a blocker for a release anymore.<br></blockquote><div><br></div><div>Indeed, I have tested this functionality and it works with out any issues at release-3.12 as well as master branch.</div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Niels<br>
<div><div class="h5"><br>
<br>
> will be tracked as part of 3.12.4<br>
><br>
> Regards,<br>
><br>
> Jiffin<br>
><br>
><br>
> On 06/11/17 11:52, Jiffin Tony Thottan wrote:<br>
> ><br>
> > Hi,<br>
> ><br>
> > It's time to prepare the 3.12.3 release, which falls on the 10th of<br>
> > each month, and hence would be 10-11-2017 this time around.<br>
> ><br>
> > This mail is to call out the following,<br>
> ><br>
> > 1) Are there any pending *blocker* bugs that need to be tracked for<br>
> > 3.12.3? If so mark them against the provided tracker [1] as blockers<br>
> > for the release, or at the very least post them as a response to this<br>
> > mail<br>
> ><br>
> > 2) Pending reviews in the 3.12 dashboard will be part of the release,<br>
> > *iff* they pass regressions and have the review votes, so use the<br>
> > dashboard [2] to check on the status of your patches to 3.12 and get<br>
> > these going<br>
> ><br>
> > 3) I have made checks on what went into 3.10 post 3.12 release and if<br>
> > these fixes are already included in 3.12 branch, then status on this is<br>
> > *green*<br>
> > as all fixes ported to 3.10, are ported to 3.12 as well.<br>
> ><br>
> > There are two patches under this category<br>
> ><br>
> > a.) <a href="https://review.gluster.org/#/c/18422/" rel="noreferrer" target="_blank">https://review.gluster.org/#/<wbr>c/18422/</a> -- Kaleb has -1 from me and<br>
> > Niels<br>
> ><br>
> > b.) <a href="https://review.gluster.org/#/c/18459/" rel="noreferrer" target="_blank">https://review.gluster.org/#/<wbr>c/18459/</a> -- @Gunther, can u pls trigger<br>
> > regression for this patch(give verified +1 from gerrit)<br>
> ><br>
> ><br>
> > Thanks,<br>
> > Jiffin<br>
> ><br>
> > [1] Release bug tracker:<br>
> > <a href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.12.3" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>show_bug.cgi?id=glusterfs-3.<wbr>12.3</a><br>
> ><br>
> > [2] 3.12 review dashboard:<br>
> > <a href="https://review.gluster.org/#/projects/glusterfs,dashboards/dashboard:3-12-dashboard" rel="noreferrer" target="_blank">https://review.gluster.org/#/<wbr>projects/glusterfs,dashboards/<wbr>dashboard:3-12-dashboard</a><br>
> ><br>
> ><br>
><br>
</div></div>______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br>
</blockquote></div><br></div></div>