On Mon, Jul 11, 2016 at 2:19 AM, Sean Owen <so...@cloudera.com> wrote: > branch-2.0 should really still be 2.0.0-SNAPSHOT, technically. I think > that was accidentally updated in the RC release.
Actually it's correct, even if at first sight it might appear wrong. The tag that is being voted on (rc2) has the "2.0.0" release. So, technically, anything after that tag is after 2.0.0, so that in case the vote passes, there's no need to push a commit that "fixes" the version number to be 2.0.1-SNAPSHOT. If the event of an rc3, as part of preparing the rc, the version will be reverted to "2.0.0" and a new commit added after the rc3 tag to forward the version to 2.0.1-SNAPSHOT. See commits: 4a55b2326c8cf50f772907a8b73fd5e7b3d1aa06 6e8fa86ebf30a9b850f4a66810d5d38d1f188b33 -- Marcelo --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
