Great! Thank you!
Bests,
Dongjoon.
On Thu, Oct 17, 2019 at 10:19 Xingbo Jiang wrote:
> I've deleted the branch-3.0-preview branch, and added `3.0.0-preview` tag
> to master (https://github.com/apache/spark/releases/tag/3.0.0-preview).
> I'll be working on make a RC now.
>
> Cheers,
>
> Xingbo
>
I've deleted the branch-3.0-preview branch, and added `3.0.0-preview` tag
to master (https://github.com/apache/spark/releases/tag/3.0.0-preview).
I'll be working on make a RC now.
Cheers,
Xingbo
Sean Owen 于2019年10月17日周四 下午4:23写道：
> Sure, if that works, that's a simpler solution. The preview re
Sure, if that works, that's a simpler solution. The preview release is
like an RC of the master branch itself.
Are there any issues with that approach right now?
Yes if it turns out that we can't get a reasonably stable release off
master, then we can branch and cherry-pick. We'd have to retain the
How about add `3.0.0-preview` tag on master branch, and claim that for the
preview release, we won't consider bugs introduced by new features merged
into master after the first preview RC ? This could rule out the risk that
we keep on import new commits and need to resolve more critical bugs thus
t
