Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3624#issuecomment-66204351
@tgravescs It should be fine to pull docs-only changes into `branch-1.2`.
We're trying to hold off on merging code changes that aren't addressing 1.2.0
release blockers because we don't want to risk introducing new regressions and
having to call new votes. If you do want to merge a code change that should
eventually be backported into `branch-1.2`, just merge it into the other
branches, leave its JIRA open with 1.2.1 listed in Target Version/s and not Fix
Version/s, then add the `backport-needed` label to the issue so that we
remember to come back to it after 1.2.0 is released.
---
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]
