Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10108#issuecomment-161417626
@pwendell this should probably be announced on the list when you start or
else we might have a very small chance of a race condition in tagging/merging
things.
I get the point that your first half of the fix could conceivably end up in
1.6.0 and not the other, but is that a good thing? you made a second JIRA
anyway I see, so one of them needs to be associated here.
I think we have a larger problem, as ever in Spark, if people are just
merging fixes right up to and well past the deadline. We were supposed to be
cutting RCs 3 weeks ago, but it arbitrarily happened now.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
