<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi, <br>
<br>
It's time to prepare the 3.12.5 release, which falls on the 10th
of <br>
each month, and hence would be 12-01-2018 this time around. <br>
<br>
This mail is to call out the following, <br>
<br>
1) Are there any pending <b class="moz-txt-star"><span
class="moz-txt-tag">*</span>blocker<span class="moz-txt-tag">*</span></b>
bugs that need to be tracked for <br>
3.12.5? 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>
<b class="moz-txt-star"><span class="moz-txt-tag">*</span>iff<span
class="moz-txt-tag">*</span></b> 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 <b class="moz-txt-star"><span class="moz-txt-tag">*</span>green<span
class="moz-txt-tag">*</span></b> <br>
as all fixes ported to 3.10, are ported to 3.12 as well. <br>
</p>
Thanks, <br>
Jiffin <br>
<br>
[1] Release bug tracker: <br>
<a class="moz-txt-link-freetext"
href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.12.2">https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.12.5</a><br>
<br>
[2] 3.12 review dashboard: <br>
<a class="moz-txt-link-freetext"
href="https://review.gluster.org/#/projects/glusterfs,dashboards/dashboard:3-12-dashboard">https://review.gluster.org/#/projects/glusterfs,dashboards/dashboard:3-12-dashboard</a>
</body>
</html>