Would it be possible to have the following backported to 3.12:
See my mail with subject "New 3.12.7 possible split-brain on replica 3" on the
list earlier this week for more details.
Thank you very much.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On April 11, 2018 5:16 AM, Jiffin Tony Thottan <jthot...@redhat.com> wrote:
> It's time to prepare the 3.12.8 release, which falls on the 10th of
> each month, and hence would be 12-04-2018 this time around.
> This mail is to call out the following,
> 1) Are there any pending *blocker* bugs that need to be tracked for
> 3.12.7? If so mark them against the provided tracker  as blockers
> for the release, or at the very least post them as a response to this
> 2) Pending reviews in the 3.12 dashboard will be part of the release,
> *iff* they pass regressions and have the review votes, so use the
> dashboard  to check on the status of your patches to 3.12 and get
> these going
> 3) I have made checks on what went into 3.10 post 3.12 release and if
> these fixes are already included in 3.12 branch, then status on this is
> as all fixes ported to 3.10, are ported to 3.12 as well.
> IMO https://review.gluster.org/19659 is like a minor feature to me. Can
> please provide a justification for why it need to include in 3.12 stable
> And please rebase the change as well
> The smoke failed for https://review.gluster.org/#/c/19818/. Can please check
> the same?
>  Release bug tracker:
>  3.12 review dashboard:
Gluster-users mailing list