+1
Agree with Shyam. We can make more releases, but let's not stop release cycle.
On 12-Oct-2017 8:32 PM, "Shyam Ranganathan" <srangana@xxxxxxxxxx> wrote:
On 10/12/2017 08:09 AM, Jiffin Tony Thottan wrote: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).
Hi,
[2] : https://review.gluster.org/#/c/18489/
[1] : https://review.gluster.org/18506
<https://review.gluster.org/18506 >
Both issues looks like a regression. Master patch [2] got merged in master but [1] 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.
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).
Thanks,
Shyam
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
