Thanks, Dongjoon!
I did it.
Best,
Takeshi
On Sun, Jan 13, 2019 at 9:33 AM Dongjoon Hyun
wrote:
> Hi, Takeshi.
>
> Please start a new thread by using a new title containing `2.3.3`.
>
> Bests,
> Dongjoon.
>
> On Sat, Jan 12, 2019 at 3:39 PM Takeshi Yamamuro
> wrote:
>
>> Hi, all
>>
>> I'm
Hi, Takeshi.
Please start a new thread by using a new title containing `2.3.3`.
Bests,
Dongjoon.
On Sat, Jan 12, 2019 at 3:39 PM Takeshi Yamamuro
wrote:
> Hi, all
>
> I'm planning to start the release vote for v2.3.3 in the start of the next
> week.
> # I've already checked that all the tests
Hi, all
I'm planning to start the release vote for v2.3.3 in the start of the next
week.
# I've already checked that all the tests passed in branch-2.3 and
# there is no problem by the release scripts with dry-run.
If there is any problem, please ping me.
Best,
Takeshi
On Wed, Jan 9, 2019 at
Thank you, Takeshi!
Dongjoon Hyun 于2019年1月8日周二 下午10:13写道：
> Great! Thank you, Takeshi! :D
>
> Bests,
> Dongjoon.
>
> On Tue, Jan 8, 2019 at 8:47 PM Takeshi Yamamuro
> wrote:
>
>> If there is no other volunteer for the release of 2.3.3, I'd like to.
>>
>> best,
>> takeshi
>>
>> On Fri, Jan 4,
Great! Thank you, Takeshi! :D
Bests,
Dongjoon.
On Tue, Jan 8, 2019 at 8:47 PM Takeshi Yamamuro
wrote:
> If there is no other volunteer for the release of 2.3.3, I'd like to.
>
> best,
> takeshi
>
> On Fri, Jan 4, 2019 at 11:49 AM Dongjoon Hyun
> wrote:
>
>> Thank you, Sean!
>>
>> Bests,
>>
If there is no other volunteer for the release of 2.3.3, I'd like to.
best,
takeshi
On Fri, Jan 4, 2019 at 11:49 AM Dongjoon Hyun
wrote:
> Thank you, Sean!
>
> Bests,
> Dongjoon.
>
>
> On Thu, Jan 3, 2019 at 2:50 PM Sean Owen wrote:
>
>> Yes, that one's not going to be back-ported to 2.3. I
Thank you, Sean!
Bests,
Dongjoon.
On Thu, Jan 3, 2019 at 2:50 PM Sean Owen wrote:
> Yes, that one's not going to be back-ported to 2.3. I think it's fine to
> proceed with a 2.2 release with what's there now and call it done.
> Note that Spark 2.3 would be EOL around September of this year.
>
Yes, that one's not going to be back-ported to 2.3. I think it's fine to
proceed with a 2.2 release with what's there now and call it done.
Note that Spark 2.3 would be EOL around September of this year.
On Thu, Jan 3, 2019 at 2:31 PM Dongjoon Hyun
wrote:
> Thank you for additional support for
>> +1 on 2.2.3 of course
>>
>>
>> --
>> *From:* Dongjoon Hyun
>> *Sent:* Wednesday, January 2, 2019 12:21 PM
>> *To:* Saisai Shao
>> *Cc:* Xiao Li; Felix Cheung; Sean Owen; dev
>> *Subject:* Re: Apache Spark 2.2.3 ?
>>
y, January 2, 2019 12:21 PM
> *To:* Saisai Shao
> *Cc:* Xiao Li; Felix Cheung; Sean Owen; dev
> *Subject:* Re: Apache Spark 2.2.3 ?
>
> Thank you for swift feedbacks and Happy New Year. :)
> For 2.2.3 release on next week, I see two positive opinions (including
> mine)
> and d
+1 on 2.2.3 of course
From: Dongjoon Hyun
Sent: Wednesday, January 2, 2019 12:21 PM
To: Saisai Shao
Cc: Xiao Li; Felix Cheung; Sean Owen; dev
Subject: Re: Apache Spark 2.2.3 ?
Thank you for swift feedbacks and Happy New Year. :)
For 2.2.3 release on next week
nce 2.3.2... (Sept 2018)
>>>
>>> And 2 months since 2.4.0 (Nov 2018) - does the community feel 2.4 branch
>>> is stabilizing?
>>>
>>>
>>> ----------
>>> *From:* Sean Owen
>>> *Sent:* Tuesday, January 1, 2019 8:30
t;
>> --
>> *From:* Sean Owen
>> *Sent:* Tuesday, January 1, 2019 8:30 PM
>> *To:* Dongjoon Hyun
>> *Cc:* dev
>> *Subject:* Re: Apache Spark 2.2.3 ?
>>
>> I agree with that logic, and if you're volunteering to do the legwork,
&
Speaking of, it’s been 3 months since 2.3.2... (Sept 2018)
And 2 months since 2.4.0 (Nov 2018) - does the community feel 2.4 branch is
stabilizing?
From: Sean Owen
Sent: Tuesday, January 1, 2019 8:30 PM
To: Dongjoon Hyun
Cc: dev
Subject: Re: Apache Spark 2.2.3
I agree with that logic, and if you're volunteering to do the legwork,
I don't see a reason not to cut a final 2.2 release.
On Tue, Jan 1, 2019 at 9:19 PM Dongjoon Hyun wrote:
>
> Hi, All.
>
> Apache Spark community has a policy maintaining the feature branch for 18
> months. I think it's time
15 matches
Mail list logo
