<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 20, 2017 at 7:37 PM, Shyam <span dir="ltr"><<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Release tagging has been postponed by a day to accommodate a fix for a regression that has been introduced between 3.11.0 and 3.11.1 (see [1] for details).<br>
<br>
As a result 3.11.1 will be tagged on the 21st June as of now (further delays will be notified to the lists appropriately).<br></blockquote><div><br></div><div>The required patches landed upstream for review and are undergoing review. Could we do the tagging tomorrow? We don't want to rush the patches to make sure we don't introduce any new bugs at this time.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks,<br>
Shyam<br>
<br>
[1] Bug awaiting fix: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1463250" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/sh<wbr>ow_bug.cgi?id=1463250</a><span class=""><br>
<br>
"Releases are made better together"<br>
<br></span><span class="">
On 06/06/2017 09:24 AM, Shyam wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
Hi,<br>
<br>
It's time to prepare the 3.11.1 release, which falls on the 20th of<br>
each month [4], and hence would be June-20th-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.11.1? 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.11 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.11 and get<br>
these going<br>
<br>
3) Empty release notes are posted here [3], if there are any specific<br>
call outs for 3.11 beyond bugs, please update the review, or leave a<br>
comment in the review, for us to pick it up<br>
<br>
Thanks,<br>
Shyam/Kaushal<br>
<br>
[1] Release bug tracker:<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.11.1" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/sh<wbr>ow_bug.cgi?id=glusterfs-3.11.1</a><br>
<br>
[2] 3.11 review dashboard:<br>
<a href="https://review.gluster.org/#/projects/glusterfs,dashboards/dashboard:3-11-dashboard" rel="noreferrer" target="_blank">https://review.gluster.org/#/p<wbr>rojects/glusterfs,dashboards/d<wbr>ashboard:3-11-dashboard</a><br>
<br>
<br>
[3] Release notes WIP: <a href="https://review.gluster.org/17480" rel="noreferrer" target="_blank">https://review.gluster.org/174<wbr>80</a><br>
<br>
[4] Release calendar: <a href="https://www.gluster.org/community/release-schedule/" rel="noreferrer" target="_blank">https://www.gluster.org/commun<wbr>ity/release-schedule/</a><br>
______________________________<wbr>_________________<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://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-devel</a><br>
</blockquote><div class="HOEnZb"><div class="h5">
______________________________<wbr>_________________<br>
maintainers mailing list<br>
<a href="mailto:maintainers@gluster.org" target="_blank">maintainers@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/maintainers</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Pranith<br></div></div>
</div></div>