[Gluster-devel] [Gluster-Maintainers] [Gluster-users] Release 3.12.2 : Scheduled for the 10th of October
srangana at redhat.com
Thu Oct 12 15:02:16 UTC 2017
On 10/12/2017 08:09 AM, Jiffin Tony Thottan wrote:
>>  : https://review.gluster.org/#/c/18489/
>>  : https://review.gluster.org/18506
> Both issues looks like a regression. Master patch  got merged in
> master but  is still pending.
> @Rafi : Can you get the reviews done ASAP and merge it on master.
> I hope both can be make it in 3.12 before the time deadline. If not
> please let me know.
Yes, both issues are a regression, but the release deadline is past, it
can always land in the next release or in an async release (3.12.2-2) if
there is a need from users to absolutely have these fixes earlier in the
builds. Further these have existed since 3.12.0 (If I read this right).
I suggest the release train continue on schedule and not wait in the
future. Think about what we would have done if we found these issues an
hour after release tagging (or the release announcement for that matter).
More information about the Gluster-devel