<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Mabi,</p>
<p>I have checked with afr maintainer, all of the required changes
is merged in 3.12.</p>
<p>Hence moving forward with 3.12.12 release<br>
</p>
<p>Regards,</p>
<p>Jiffin<br>
</p>
<br>
<div class="moz-cite-prefix">On Monday 09 July 2018 01:04 PM, mabi
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:-3-l90hgz9hT0dMOF59jRo_7ZOlPzH5OEYXcLXA8QR_bqFPSJIcyjD2s7x_IkqRAEh_UA0dNJcGhR7ojEc5g3J-y095lvaNBqUyx1Vpb1Co=@protonmail.ch">
<div>Hi Jiffin,<br>
</div>
<div><br>
</div>
<div>Based on the issues I am encountering on a nearly daily basis
(See "<span>New 3.12.7 possible split-brain on replica 3" thread
in this ML) since now already 2-3 months I would be really
glad if the required fixes as mentioned by Ravi could make it
into the 3.12.12 release. Ravi mentioned the following:</span><br>
</div>
<div><br>
</div>
<div>afr: heal gfids when file is not present on all bricks<br>
</div>
<div>afr: don't update readables if inode refresh failed on all
children<br>
</div>
<div>afr: fix bug-1363721.t failure<br>
</div>
<div>afr: add quorum checks in pre-op<br>
</div>
<div>afr: don't treat all cases all bricks being blamed as
split-brain<br>
</div>
<div>afr: capture the correct errno in post-op quorum check<br>
</div>
<div>afr: add quorum checks in post-op<br>
</div>
<div><br>
</div>
<div>Right now I only see the first one pending in the review
dashboard. It would be great if all of them could make it into
this release.<br>
</div>
<div><br>
</div>
<div>Best regards,<br>
</div>
<div>Mabi<br>
</div>
<div class="protonmail_signature_block
protonmail_signature_block-empty">
<div class="protonmail_signature_block-user
protonmail_signature_block-empty">
<div><br>
</div>
</div>
<div class="protonmail_signature_block-proton
protonmail_signature_block-empty"><br>
</div>
</div>
<div><br>
</div>
<div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br>
</div>
<div> On July 9, 2018 7:18 AM, Jiffin Tony Thottan
<a class="moz-txt-link-rfc2396E" href="mailto:jthottan@redhat.com"><jthottan@redhat.com></a> wrote:<br>
</div>
<div> <br>
</div>
<blockquote class="protonmail_quote" type="cite">
<div>Hi, <br>
</div>
<div> <br>
</div>
<div> It's time to prepare the 3.12.12 release, which falls on
the 10th of <br>
</div>
<div> each month, and hence would be 11-07-2018 this time
around. <br>
</div>
<div> <br>
</div>
<div> This mail is to call out the following, <br>
</div>
<div> <br>
</div>
<div> 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>
</div>
<div> 3.12.12? If so mark them against the provided tracker [1]
as blockers <br>
</div>
<div> for the release, or at the very least post them as a
response to this <br>
</div>
<div> mail <br>
</div>
<div> <br>
</div>
<div> 2) Pending reviews in the 3.12 dashboard will be part of
the release, <br>
</div>
<div> <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>
</div>
<div> dashboard [2] to check on the status of your patches to
3.12 and get <br>
</div>
<div> these going <br>
</div>
<div> <br>
</div>
<div> Thanks, <br>
</div>
<div> Jiffin <br>
</div>
<div> <br>
</div>
<div> [1] Release bug tracker: <br>
</div>
<div> <a
href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.12.12"
class="moz-txt-link-freetext" moz-do-not-send="true">https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.12.12</a>
<br>
</div>
<div> <br>
</div>
<div> [2] 3.12 review dashboard: <br>
</div>
<div> <a
href="https://review.gluster.org/#/projects/glusterfs,dashboards/dashboard:3-12-dashboard"
class="moz-txt-link-freetext" moz-do-not-send="true">https://review.gluster.org/#/projects/glusterfs,dashboards/dashboard:3-12-dashboard</a>
<br>
</div>
</blockquote>
<div><br>
</div>
</blockquote>
<br>
</body>
</html>