I don't think we would want to cut 'branch-3.0' right now, which would imply that master is 3.1. We don't want to merge every new change into two branches. It may still be useful to have `branch-3.0-preview` as a short-lived branch just used to manage the preview release, as we will need to let development on 3.0 in master continue while stabilizing the preview release with a few selected cherry-picks, but that's only of concern to the release manager.
On Wed, Oct 16, 2019 at 2:01 AM Xingbo Jiang <jiangxb1...@gmail.com> wrote: > > Hi Dongjoon, > > I'm not sure about the best practice of maintaining a preview release branch, > since new features might still go into Spark 3.0 after preview release, I > guess it might make more sense to have separated branches for 3.0.0 and > 3.0-preview. > > However, I'm open to both solutions, if we really want to reuse the branch to > also release Spark 3.0.0, then I would be happy to create a new one. > > Thanks! > > Xingbo > > Dongjoon Hyun <dongjoon.h...@gmail.com> 于2019年10月16日周三 上午6:26写道： >> >> Hi, >> >> It seems that we have `branch-3.0-preview` branch. >> >> https://github.com/apache/spark/commits/branch-3.0-preview >> >> Can we have `branch-3.0` instead of `branch-3.0-preview`? >> >> We can tag `v3.0.0-preview` on `branch-3.0` and continue to use for `v3.0.0` >> later. >> >> Bests, >> Dongjoon. --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
