I agree -- Wenchen/Reynold do you know what's the theory there? TBH I think that there has not been a 'real' release candidate yet. It's not that big a deal if these first two have been speculative RCs to get more feedback earlier for a major release, and that in fact people want to let this bake somewhat longer that the RC would imply. As long as it's converging towards fewer, more critical changes.
Excepting these merges I think that had been generally happening. It's *mostly* critical stuff now. But yeah this won't actually get released until blockers are resolved and merges slow down to what belongs in a maintenance branch. On Mon, Jul 11, 2016 at 11:08 AM, Pete Robbins <robbin...@gmail.com> wrote: > 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, --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
