Github user jburwell commented on the issue:
@koushik-das I would encourage you to discuss your concerns/perspective on
dev@ in order to allow us a community to find consensus.
There is never a good time to embark on such a freeze. I would have
propsed it earlier had the severity of situation been better understood.
However, the longer we delay addressing this raft failing tests, the longer it
will take to address them. Continuing to merge atop code that has known issues
only deepens the instability and, worse, creates a false sense of confidence
that the newly merged code is stable.
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket