Shouldn't this be a discuss thread?
I'm also happy to see more release managers and agree the time is getting
close, but we should see what features are in progress and see how close things
are and propose a date based on that. Cutting a branch to soon just creates
more work for committers to push to more branches.
http://spark.apache.org/versioning-policy.html mentioned the code freeze and
release branch cut mid-august.
Tom
On Friday, July 6, 2018, 11:47:35 AM CDT, Reynold Xin <r...@databricks.com>
wrote:
FYI 6 mo is coming up soon since the last release. We will cut the branch and
code freeze on Aug 1st in order to get 2.4 out on time.
