13 PM
To: Reynold Xin
Cc: Felix Cheung; Sean Owen; dev@spark.apache.org
Subject: Re: Kicking off the process around Spark 2.2.1
I agree, except in this case we probably want some of the fixes that are going
into the maintenance release to be present in the new feature release (like the
CRAN issue)
I agree, except in this case we probably want some of the fixes that are
going into the maintenance release to be present in the new feature release
(like the CRAN issue).
On Thu, Nov 2, 2017 at 12:12 PM, Reynold Xin wrote:
> Why tie a maintenance release to a feature release? They are supposed
Why tie a maintenance release to a feature release? They are supposed to be
independent and we should be able to make a lot of maintenance releases as
needed.
On Thu, Nov 2, 2017 at 7:13 PM Sean Owen wrote:
> The feature freeze is "mid November" :
> http://spark.apache.org/versioning-policy.html
The feature freeze is "mid November" :
http://spark.apache.org/versioning-policy.html
Let's say... Nov 15? any body have a better date?
Although it'd be nice to get 2.2.1 out sooner than later in all events, and
kind of makes sense to get out first, they need not go in order. It just
might be dist
ng; Kevin Grealish; Sean Owen
>
> *Cc:* dev@spark.apache.org
> *Subject:* Re: Kicking off the process around Spark 2.2.1
> If it’s desired I’d be happy to start on 2.3 once 2.2.1 is finished.
>
> On Thu, Nov 2, 2017 at 10:24 AM Felix Cheung
> wrote:
>
>> For the 2.2.1,
, 2017 10:38:48 AM
To: Felix Cheung; Kevin Grealish; Sean Owen
Cc: dev@spark.apache.org
Subject: Re: Kicking off the process around Spark 2.2.1
If it’s desired I’d be happy to start on 2.3 once 2.2.1 is finished.
On Thu, Nov 2, 2017 at 10:24 AM Felix Cheung
mailto:felixcheun...@hotmail.com>>
ish
> *Sent:* Thursday, November 2, 2017 9:51:56 AM
> *To:* Felix Cheung; Sean Owen; Holden Karau
> *Cc:* dev@spark.apache.org
> *Subject:* RE: Kicking off the process around Spark 2.2.1
>
>
> Any update on expected 2.2.1 (or 2.3.0) release process?
>
>
>
> *From:*
round Spark 2.2.1
Any update on expected 2.2.1 (or 2.3.0) release process?
From: Felix Cheung [mailto:felixcheun...@hotmail.com]
Sent: Thursday, October 26, 2017 10:04 AM
To: Sean Owen ; Holden Karau
Cc: dev@spark.apache.org
Subject: Re: Kicking off the process around Spark 2.2.1
Yes! I can take
Any update on expected 2.2.1 (or 2.3.0) release process?
From: Felix Cheung [mailto:felixcheun...@hotmail.com]
Sent: Thursday, October 26, 2017 10:04 AM
To: Sean Owen ; Holden Karau
Cc: dev@spark.apache.org
Subject: Re: Kicking off the process around Spark 2.2.1
Yes! I can take on RM for 2.2.1
Karau
Cc: Felix Cheung; dev@spark.apache.org
Subject: Re: Kicking off the process around Spark 2.2.1
It would be reasonably consistent with the timing of other x.y.1 releases, and
more release managers sounds useful, yeah.
Note also that in theory the code freeze for 2.3.0 starts in about 2 weeks
It would be reasonably consistent with the timing of other x.y.1 releases,
and more release managers sounds useful, yeah.
Note also that in theory the code freeze for 2.3.0 starts in about 2 weeks.
On Wed, Oct 25, 2017 at 12:29 PM Holden Karau wrote:
> Now that Spark 2.1.2 is out it seems like
Now that Spark 2.1.2 is out it seems like now is a good time to get started
on the Spark 2.2.1 release. There are some streaming fixes I’m aware of
that would be good to get into a release, is there anything else people are
working on for 2.2.1 we should be tracking?
To switch it up I’d like to su
12 matches
Mail list logo
