I would like to re-iterate that committers please be very conservative now
in merging patches into branch-2.1.
Spark is a very sophisticated (compiler, optimizer) project and sometimes
one-line changes can have huge consequences and introduce regressions. If
it is just a tiny optimization, don't m
Thanks, this was another message that went to spam for me:
http://apache-spark-developers-list.1001551.n3.nabble.com/ANNOUNCE-Apache-Spark-branch-2-1-td19688.html
Looks great -- cutting branch = in RC period.
On Tue, Nov 22, 2016 at 5:31 PM Reynold Xin wrote:
> I did send an email out with tho
I did send an email out with those information on Nov 1st. It is not meant
to be in new feature development mode anymore.
FWIW, I will cut an RC today to remind people of that. The RC will fail,
but it can serve as a good reminder.
On Tue, Nov 22, 2016 at 1:53 AM Sean Owen wrote:
> Maybe I miss
Maybe I missed it, but did anyone declare a QA period? In the past I've not
seen this, and just seen people start talking retrospectively about how
"we're in QA now" until it stops. We have
https://cwiki.apache.org/confluence/display/SPARK/Wiki+Homepage saying it
is already over, but clearly we're
To committers and contributors active in MLlib,
Thanks everyone who has started helping with the QA tasks in SPARK-18316!
I'd like to request that we stop committing non-critical changes to MLlib,
including the Python and R APIs, since still-changing public APIs make it
hard to QA. We need have a