<div dir="ltr"><br><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 19, 2017 at 11:01 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:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">3.11.1 Release tagging is tomorrow (20th June, 2017).<br>
<br>
Here are some key things to do before we tag the release,<br>
<br>
1) Regression failures: (@pranith, @maintainers)<br>
- Overall regression failures status on 3.11 since .0 release can be seen here [1]<br>
- Tests of concern are:<br>
- ./tests/basic/afr/add-brick-se<wbr>lf-heal.t [2]<br>
@pranith, this seems to be failing more often now, do we know why or any pointers?<br>
<br>
- ./tests/encryption/crypt.t [3]<br>
@maintainers? This seems to have a higher incident of failures recently on master (and just one instance on 3.11 branch). All are cores, so possibly some other change is causing this. Any updates from anyone on this?<br>
<br>
2) Pending review queue: [4] (@poornima, @csaba, @soumya, @ravishankar)<br>
- There are some reviews that do not have CentOS (or NetBSD) votes yet, and are present to be committed for over a week, I have kicked off rechecks as appropriate for some. Patch owners please keep a watch out for the same.<br>
<br>
3) Backport status: (IOW, things backported to older released branches should be present in the later ones (in this case ported to 3.8/3.10 to be present in 3.11))<br>
- This is clean as of today, pending merge of <a href="https://review.gluster.org/17512" rel="noreferrer" target="_blank">https://review.gluster.org/175<wbr>12</a><br>
<br></blockquote><div><br>Please consider <a href="https://review.gluster.org/#/c/17569/">https://review.gluster.org/#/c/17569/</a> and <a href="https://review.gluster.org/#/c/17573/">https://review.gluster.org/#/c/17573/</a> <br><br></div><div>This is requested from Kubernetes integration.<br><br></div><div>Thanks.<br></div><div>Amar<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">
Thanks,<br>
Shyam<br>
<br>
"Releases are made better together"<br>
<br>
[1] All regression failures for 3.11.1 : <a href="https://fstat.gluster.org/summary?start_date=2017-06-01&end_date=2017-06-20&branch=release-3.11" rel="noreferrer" target="_blank">https://fstat.gluster.org/summ<wbr>ary?start_date=2017-06-01&end_<wbr>date=2017-06-20&branch=release<wbr>-3.11</a><br>
<br>
[2] add-brick-self-heal.t failures: <a href="https://fstat.gluster.org/failure/2?start_date=2017-06-01&end_date=2017-06-20&branch=release-3.11" rel="noreferrer" target="_blank">https://fstat.gluster.org/fail<wbr>ure/2?start_date=2017-06-01&<wbr>end_date=2017-06-20&branch=rel<wbr>ease-3.11</a><br>
<br>
[3] crypt.t failure(s) on all branches: <a href="https://fstat.gluster.org/failure/62?start_date=2017-06-01&end_date=2017-06-20&branch=all" rel="noreferrer" target="_blank">https://fstat.gluster.org/fail<wbr>ure/62?start_date=2017-06-01&<wbr>end_date=2017-06-20&branch=all</a><br>
<br>
[4] Pending reviews needing attention: <a href="https://review.gluster.org/#/q/status:open+starredby:srangana%2540redhat.com" rel="noreferrer" target="_blank">https://review.gluster.org/#/q<wbr>/status:open+starredby:srangan<wbr>a%2540redhat.com</a><div class="gmail-HOEnZb"><div class="gmail-h5"><br>
<br>
On 06/06/2017 09:24 AM, Shyam wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
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>
</blockquote>
______________________________<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"><div dir="ltr"><div><div dir="ltr"><div>Amar Tumballi (amarts)<br></div></div></div></div></div>
</div></div></div>