Sounds good. Thanks for bringing this up!

On Wed, Dec 11, 2019 at 3:18 PM Takeshi Yamamuro <linguin....@gmail.com>
wrote:

> That looks nice, thanks!
> I checked the previous v2.4.4 release; it has around 130 commits (from
> 2.4.3 to 2.4.4), so
> I think branch-2.4 already has enough commits for the next release.
>
> A commit list from 2.4.3 to 2.4.4;
>
> https://github.com/apache/spark/compare/5ac2014e6c118fbeb1fe8e5c8064c4a8ee9d182a...7955b3962ac46b89564e0613db7bea98a1478bf2
>
> Bests,
> Takeshi
>
> On Tue, Dec 10, 2019 at 3:32 AM Sean Owen <sro...@gmail.com> wrote:
>
>> Sure, seems fine. The release cadence slows down in a branch over time
>> as there is probably less to fix, so Jan-Feb 2020 for 2.4.5 and
>> something like middle or Q3 2020 for 2.4.6 is a reasonable
>> expectation. It might plausibly be the last 2.4.x release but who
>> knows.
>>
>> On Mon, Dec 9, 2019 at 12:29 PM Dongjoon Hyun <dongjoon.h...@gmail.com>
>> wrote:
>> >
>> > Hi, All.
>> >
>> > Along with the discussion on 3.0.0, I'd like to discuss about the next
>> releases on `branch-2.4`.
>> >
>> > As we know, `branch-2.4` is our LTS branch and also there exists some
>> questions on the release plans. More releases are important not only for
>> the latest K8s version support, but also for delivering important bug fixes
>> regularly (at least until 3.x becomes dominant.)
>> >
>> > In short, I'd like to propose the followings.
>> >
>> >     1. Apache Spark 2.4.5 release (2020 January)
>> >     2. Apache Spark 2.4.6 release (2020 July)
>> >
>> > Of course, we can adjust the schedule.
>> > This aims to have a pre-defined cadence in order to give release
>> managers to prepare.
>> >
>> > Bests,
>> > Dongjoon.
>> >
>> > PS. As of now, `branch-2.4` has 135 additional patches after `2.4.4`.
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>>
>>
>
> --
> ---
> Takeshi Yamamuro
>

Reply via email to