Correction: Merging the feature work after the branch cut should not be encouraged in general, although some committers did make some exceptions based on their own judgement. We should try to avoid merging the feature work after the branch cut.
This email is a good reminder message. At least, we have two weeks ahead of the proposed branch cut date. I hope each feature owner might hurry up and try to finish it before the branch cut. Xiao Xiao Li <gatorsm...@gmail.com> 于2020年11月19日周四 下午11:36写道： > We should try to merge the feature work after the branch cut. This should > not be encouraged in general, although some committers did make some > exceptions based on their own judgement. > > This email is a good reminder message. At least, we have two weeks > ahead of the proposed branch cut date. I hope each feature owner might > hurry up and try to finish it before the branch cut. > > Xiao > > Dongjoon Hyun <dongjoon.h...@gmail.com> 于2020年11月19日周四 下午4:02写道： > >> Thank you for your volunteering! >> >> Since the previous branch-cuts were always soft-code freeze which allowed >> committers to merge to the new branches still for a while, I believe 1st >> December will be better for stabilization. >> >> Bests, >> Dongjoon. >> >> >> On Thu, Nov 19, 2020 at 3:50 PM Hyukjin Kwon <gurwls...@gmail.com> wrote: >> >>> Hi all, >>> >>> I think we haven’t decided yet the exact branch-cut, code freeze and >>> release manager. >>> >>> As we planned in https://spark.apache.org/versioning-policy.html >>> >>> Early Dec 2020 Code freeze. Release branch cut >>> >>> Code freeze and branch cutting is coming. >>> >>> Therefore, we should finish if there are any remaining works for Spark >>> 3.1, and >>> switch to QA mode soon. >>> I think it’s time to set to keep it on track, and I would like to >>> volunteer to help drive this process. >>> >>> I am currently thinking 4th Dec as the branch-cut date. >>> >>> Any thoughts? >>> >>> Thanks all. >>> >>>
