<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 21, 2017 at 9:12 PM, Shyam <span dir="ltr">&lt;<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">On 06/21/2017 11:37 AM, Pranith Kumar Karampuri wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">
<br>
<br>
On Tue, Jun 20, 2017 at 7:37 PM, Shyam &lt;<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a><br></span><span class="gmail-">
&lt;mailto:<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>&gt;&gt; wrote:<br>
<br>
    Hi,<br>
<br>
    Release tagging has been postponed by a day to accommodate a fix for<br>
    a regression that has been introduced between 3.11.0 and 3.11.1 (see<br>
    [1] for details).<br>
<br>
    As a result 3.11.1 will be tagged on the 21st June as of now<br>
    (further delays will be notified to the lists appropriately).<br>
<br>
<br>
The required patches landed upstream for review and are undergoing<br>
review. Could we do the tagging tomorrow? We don&#39;t want to rush the<br>
patches to make sure we don&#39;t introduce any new bugs at this time.<br>
</span></blockquote>
<br>
Agreed, considering the situation we would be tagging the release tomorrow (June-22nd 2017).<br></blockquote><div><br></div><div>Status of afr/ec patches:<br><br></div><div>EC patch on master: <a href="https://review.gluster.org/17594">https://review.gluster.org/17594</a><br></div><div>EC patch on release-3.11: <a href="https://review.gluster.org/17615">https://review.gluster.org/17615</a><br><br></div><div>Master patch is already merged, and 3.11 patch: <a href="https://review.gluster.org/17602">https://review.gluster.org/17602</a><br><br></div><div>DHT patch: <a href="https://review.gluster.org/17595">https://review.gluster.org/17595</a>, I guess this patch needs review as well as regression results.<br><br></div><div>At the moment we are awaiting regression results of all these patches.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="gmail-h5">
<br>
<br>
<br>
    Thanks,<br>
    Shyam<br>
<br>
    [1] Bug awaiting fix:<br>
    <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><br>
    &lt;<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1463250" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/s<wbr>how_bug.cgi?id=1463250</a>&gt;<br>
<br>
    &quot;Releases are made better together&quot;<br>
<br>
    On 06/06/2017 09:24 AM, Shyam wrote:<br>
<br>
        Hi,<br>
<br>
        It&#39;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<br>
        this<br>
        mail<br>
<br>
        2) Pending reviews in the 3.11 dashboard will be part of the<br>
        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<br>
        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>
        &lt;<a href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.11.1" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/s<wbr>how_bug.cgi?id=glusterfs-3.11.<wbr>1</a>&gt;<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>
        &lt;<a href="https://review.gluster.org/#/projects/glusterfs,dashboards/dashboard:3-11-dashboard" rel="noreferrer" target="_blank">https://review.gluster.org/#/<wbr>projects/glusterfs,dashboards/<wbr>dashboard:3-11-dashboard</a>&gt;<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>
        &lt;<a href="https://review.gluster.org/17480" rel="noreferrer" target="_blank">https://review.gluster.org/17<wbr>480</a>&gt;<br>
<br>
        [4] Release calendar:<br>
        <a href="https://www.gluster.org/community/release-schedule/" rel="noreferrer" target="_blank">https://www.gluster.org/commun<wbr>ity/release-schedule/</a><br>
        &lt;<a href="https://www.gluster.org/community/release-schedule/" rel="noreferrer" target="_blank">https://www.gluster.org/commu<wbr>nity/release-schedule/</a>&gt;<br>
        ______________________________<wbr>_________________<br>
        Gluster-devel mailing list<br></div></div>
        <a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a> &lt;mailto:<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.<wbr>org</a>&gt;<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><span class="gmail-"><br>
        &lt;<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/mail<wbr>man/listinfo/gluster-devel</a>&gt;<br>
<br>
    ______________________________<wbr>_________________<br>
    maintainers mailing list<br></span><span class="gmail-">
    <a href="mailto:maintainers@gluster.org" target="_blank">maintainers@gluster.org</a> &lt;mailto:<a href="mailto:maintainers@gluster.org" target="_blank">maintainers@gluster.or<wbr>g</a>&gt;<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>
    &lt;<a href="http://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://lists.gluster.org/mail<wbr>man/listinfo/maintainers</a>&gt;<br>
<br>
<br>
<br>
<br>
--<br>
Pranith<br>
</span></blockquote>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr">Pranith<br></div></div>
</div></div>