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
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 e
i'm going to be upgrading jenkins to something more reasonable, and there
will definitely be some downtime as i get things sorted.
we should be back up and building by monday.
shane
--
Shane Knapp
Computer Guy / Voice of Reason
UC Berkeley EECS Research / RISELab Staff Technical Lead
https://ris
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 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 r
