spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reynold Xin <>
Subject Re: Please limit commits for branch-2.1
Date Tue, 22 Nov 2016 17:30:55 GMT
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 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
> saying it
> is already over, but clearly we're not doing RCs.
> We should make this more formal and predictable. We probably need a
> clearer definition of what changes in QA. I'm moving the wiki to
> now and could try to put up some words around this when
> I move this page above today.
> On Mon, Nov 21, 2016 at 11:20 PM Joseph Bradley <>
> wrote:
> 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 already started to sign off on some QA tasks, but
> we may need to re-open them if changes are committed, especially if those
> changes are to public APIs.  There's no need to push Python and R wrappers
> into 2.1 at the last minute.
> Let's focus on completing QA, after which we can resume committing API
> changes to master (not branch-2.1).
> Thanks everyone!
> Joseph
> --
> Joseph Bradley
> Software Engineer - Machine Learning
> Databricks, Inc.
> [image:] <>

View raw message