Can we just tag master? On Wed, Oct 16, 2019 at 12:34 AM, Wenchen Fan < cloud0...@gmail.com > wrote:
> > Does anybody remember what we did for 2.0 preview? Personally I'd like to > avoid cutting branch-3.0 right now, otherwise we need to merge PRs into > two branches in the following several months. > > > Thanks, > Wenchen > > On Wed, Oct 16, 2019 at 3:01 PM Xingbo Jiang < jiangxb1987@ gmail. com ( > 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. hyun@ gmail. com ( 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 ( >>> 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. >>> >> >> > >
