+1 for maintenance release, and also +1 for doing this in Jan !

Thanks,
Mridul

On Tue, Dec 7, 2021 at 11:41 PM Gengliang Wang <ltn...@gmail.com> wrote:

> +1 for new maintenance releases for all 3.x branches as well.
>
> On Wed, Dec 8, 2021 at 8:19 AM Hyukjin Kwon <gurwls...@gmail.com> wrote:
>
>> SGTM!
>>
>> On Wed, 8 Dec 2021 at 09:07, huaxin gao <huaxin.ga...@gmail.com> wrote:
>>
>>> I prefer to start rolling the release in January if there is no need to
>>> publish it sooner :)
>>>
>>> On Tue, Dec 7, 2021 at 3:59 PM Hyukjin Kwon <gurwls...@gmail.com> wrote:
>>>
>>>> Oh BTW, I realised that it's a holiday season soon this month including
>>>> Christmas and new year.
>>>> Shall we maybe start rolling the release around next January? I would
>>>> leave it to @huaxin gao <huaxin.ga...@gmail.com> :-).
>>>>
>>>> On Wed, 8 Dec 2021 at 06:19, Dongjoon Hyun <dongjoon.h...@gmail.com>
>>>> wrote:
>>>>
>>>>> +1 for new releases.
>>>>>
>>>>> Dongjoon.
>>>>>
>>>>> On Mon, Dec 6, 2021 at 8:51 PM Wenchen Fan <cloud0...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> +1 to make new maintenance releases for all 3.x branches.
>>>>>>
>>>>>> On Tue, Dec 7, 2021 at 8:57 AM Sean Owen <sro...@gmail.com> wrote:
>>>>>>
>>>>>>> Always fine by me if someone wants to roll a release.
>>>>>>>
>>>>>>> It's been ~6 months since the last 3.0.x and 3.1.x releases, too; a
>>>>>>> new release of those wouldn't hurt either, if any of our release 
>>>>>>> managers
>>>>>>> have the time or inclination. 3.0.x is reaching unofficial end-of-life
>>>>>>> around now anyway.
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Dec 6, 2021 at 6:55 PM Hyukjin Kwon <gurwls...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> It's been two months since Spark 3.2.0 release, and we have
>>>>>>>> resolved many bug fixes and regressions. What do you guys think about
>>>>>>>> rolling Spark 3.2.1 release?
>>>>>>>>
>>>>>>>> cc @huaxin gao <huaxin.ga...@gmail.com> FYI who I happened to
>>>>>>>> overhear that is interested in rolling the maintenance release :-).
>>>>>>>>
>>>>>>>

Reply via email to