<div>Thank you Ravi for your comments. I do understand that it might not be very wise to risk any mistakes by rushing this fix into 3.12.8. In that case I will be more patient and wait for 3.12.9 next month.<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 April 11, 2018 5:09 PM, Ravishankar N <ravishankar@redhat.com> wrote:<br></div><div> <br></div><blockquote class="protonmail_quote" type="cite"><div>Mabi,<br></div><div> <br></div><div> It looks like one of the patches is not a straight forward
cherry-pick to the 3.12 branch. Even though the conflict might be
easy to resolve, I don't think it is a good idea to hurry it for
tomorrow. We will definitely have it ready by the next minor release
(or if by chance the release is delayed and the back port is
reviewed and merged before that). Hope that is acceptable.<br></div><div> <br></div><div> -Ravi<br></div><div> <br></div><div> <br></div><div class="moz-cite-prefix">On 04/11/2018 01:11 PM, mabi wrote:<br></div><blockquote type="cite"><div>Dear Jiffin,<br></div><div><br></div><div>Would it be possible to have the following backported to
3.12:<br></div><div><br></div><div><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1482064">https://bugzilla.redhat.com/show_bug.cgi?id=1482064</a><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>See my mail with subject "New 3.12.7 possible split-brain on
replica 3" on the list earlier this week for more details. <br></div><div><br></div><div>Thank you very much.<br></div><div><div><br></div><div>Best regards,<br></div></div><div>Mabi<br></div><div><br></div><div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br></div><div>On April 11, 2018 5:16 AM, Jiffin Tony Thottan <a href="mailto:jthottan@redhat.com" class="moz-txt-link-rfc2396E"><jthottan@redhat.com></a> wrote:<br></div><div><br></div><blockquote type="cite" class="protonmail_quote"><div>Hi, <br></div><div><br></div><div>It's time to prepare the 3.12.8 release, which falls on
the 10th of <br></div><div>each month, and hence would be 12-04-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.7? 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>3) I have made checks on what went into 3.10 post 3.12
release and if <br></div><div>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></div><div>as all fixes ported to 3.10, are ported to 3.12 as well. <br></div><p>@Mlind <br></p><p>IMO <a class="moz-txt-link-freetext" href="https://review.gluster.org/19659">https://review.gluster.org/19659</a> is like a minor feature to me. Can please provide a
justification for why it need to include in 3.12 stable
release?<br></p><p>And please rebase the change as well<br></p><p>@Raghavendra<br></p><p>The smoke failed for <a class="moz-txt-link-freetext" href="https://review.gluster.org/#/c/19818/">https://review.gluster.org/#/c/19818/</a>.
Can please check the same?<br></p><div>Thanks,<br></div><div>Jiffin <br></div><div><br></div><div>[1] Release bug tracker: <br></div><div><a class="moz-txt-link-freetext" href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.12.8">https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.12.8</a><br></div><div><br></div><div>[2] 3.12 review dashboard: <br></div><div><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><br></div></blockquote><div><br></div><div><br></div><div><br></div><pre wrap="">_______________________________________________
Gluster-users mailing list
<a href="mailto:Gluster-users@gluster.org" class="moz-txt-link-abbreviated">Gluster-users@gluster.org</a>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" class="moz-txt-link-freetext">http://lists.gluster.org/mailman/listinfo/gluster-users</a><br></pre></blockquote></blockquote><div><br></div>