It looks like the vote on 2.0-rc2 will not pass so there will be a new RC from the 2.0 branch. With a project management hat on I would expect to see only fixes to the remaining blocker issues or high priority bug fixes going into the 2.0 branch as defect burn down. However, I see several new functional PRs which were originally targeted at 2.1 being merged into branch-2.0 (eg children of https://issues.apache.org/jira/browse/SPARK-16275 ) and these will now be in the upcoming 2.0-RC3.
I assume these are zero risk changes that will not further delay a 2.0 release. Cheers,
