[DISCUSS] Exact feature freeze date

classic Classic list List threaded Threaded
25 messages Options
12
Reply | Threaded
Open this post in threaded view
|

[DISCUSS] Exact feature freeze date

Stephan Ewen
Hi all!

I want to bring up a discussion about when we want to do the feature freeze
for 1.11.

When kicking off the release cycle, we tentatively set the date to end of
April, which would be in one week.

I can say from the features I am involved with (FLIP-27, FLIP-115,
reviewing some state backend improvements, etc.) that it would be helpful
to have two additional weeks.

When looking at various other feature threads, my feeling is that there are
more contributors and committers that could use a few more days.
The last two months were quite exceptional in and we did lose a bit of
development speed here and there.

How do you think about making *May 15th* the feature freeze?

Best,
Stephan
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Exact feature freeze date

Piotr Nowojski-3
Hi Stephan,

As release manager I’ve seen that quite a bit of features could use of the extra couple of weeks. This also includes some features that I’m involved with, like FLIP-76, or limiting the in-flight buffers.

+1 From my side for extending the feature freeze until May 15th.

Piotrek

> On 23 Apr 2020, at 10:10, Stephan Ewen <[hidden email]> wrote:
>
> Hi all!
>
> I want to bring up a discussion about when we want to do the feature freeze
> for 1.11.
>
> When kicking off the release cycle, we tentatively set the date to end of
> April, which would be in one week.
>
> I can say from the features I am involved with (FLIP-27, FLIP-115,
> reviewing some state backend improvements, etc.) that it would be helpful
> to have two additional weeks.
>
> When looking at various other feature threads, my feeling is that there are
> more contributors and committers that could use a few more days.
> The last two months were quite exceptional in and we did lose a bit of
> development speed here and there.
>
> How do you think about making *May 15th* the feature freeze?
>
> Best,
> Stephan

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Exact feature freeze date

Till Rohrmann
+1 for extending the feature freeze until May 15th.

Cheers,
Till

On Thu, Apr 23, 2020 at 1:00 PM Piotr Nowojski <[hidden email]> wrote:

> Hi Stephan,
>
> As release manager I’ve seen that quite a bit of features could use of the
> extra couple of weeks. This also includes some features that I’m involved
> with, like FLIP-76, or limiting the in-flight buffers.
>
> +1 From my side for extending the feature freeze until May 15th.
>
> Piotrek
>
> > On 23 Apr 2020, at 10:10, Stephan Ewen <[hidden email]> wrote:
> >
> > Hi all!
> >
> > I want to bring up a discussion about when we want to do the feature
> freeze
> > for 1.11.
> >
> > When kicking off the release cycle, we tentatively set the date to end of
> > April, which would be in one week.
> >
> > I can say from the features I am involved with (FLIP-27, FLIP-115,
> > reviewing some state backend improvements, etc.) that it would be helpful
> > to have two additional weeks.
> >
> > When looking at various other feature threads, my feeling is that there
> are
> > more contributors and committers that could use a few more days.
> > The last two months were quite exceptional in and we did lose a bit of
> > development speed here and there.
> >
> > How do you think about making *May 15th* the feature freeze?
> >
> > Best,
> > Stephan
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Exact feature freeze date

Aljoscha Krettek-2
+1

Aljoscha

On 23.04.20 15:23, Till Rohrmann wrote:

> +1 for extending the feature freeze until May 15th.
>
> Cheers,
> Till
>
> On Thu, Apr 23, 2020 at 1:00 PM Piotr Nowojski <[hidden email]> wrote:
>
>> Hi Stephan,
>>
>> As release manager I’ve seen that quite a bit of features could use of the
>> extra couple of weeks. This also includes some features that I’m involved
>> with, like FLIP-76, or limiting the in-flight buffers.
>>
>> +1 From my side for extending the feature freeze until May 15th.
>>
>> Piotrek
>>
>>> On 23 Apr 2020, at 10:10, Stephan Ewen <[hidden email]> wrote:
>>>
>>> Hi all!
>>>
>>> I want to bring up a discussion about when we want to do the feature
>> freeze
>>> for 1.11.
>>>
>>> When kicking off the release cycle, we tentatively set the date to end of
>>> April, which would be in one week.
>>>
>>> I can say from the features I am involved with (FLIP-27, FLIP-115,
>>> reviewing some state backend improvements, etc.) that it would be helpful
>>> to have two additional weeks.
>>>
>>> When looking at various other feature threads, my feeling is that there
>> are
>>> more contributors and committers that could use a few more days.
>>> The last two months were quite exceptional in and we did lose a bit of
>>> development speed here and there.
>>>
>>> How do you think about making *May 15th* the feature freeze?
>>>
>>> Best,
>>> Stephan
>>
>>
>

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Exact feature freeze date

Timo Walther-2
 From the SQL side, I'm sure that FLIP-95 and FLIP-105 could benefit
from extending the feature freeze.

Thanks,
Timo

On 23.04.20 16:11, Aljoscha Krettek wrote:

> +1
>
> Aljoscha
>
> On 23.04.20 15:23, Till Rohrmann wrote:
>> +1 for extending the feature freeze until May 15th.
>>
>> Cheers,
>> Till
>>
>> On Thu, Apr 23, 2020 at 1:00 PM Piotr Nowojski <[hidden email]>
>> wrote:
>>
>>> Hi Stephan,
>>>
>>> As release manager I’ve seen that quite a bit of features could use
>>> of the
>>> extra couple of weeks. This also includes some features that I’m
>>> involved
>>> with, like FLIP-76, or limiting the in-flight buffers.
>>>
>>> +1 From my side for extending the feature freeze until May 15th.
>>>
>>> Piotrek
>>>
>>>> On 23 Apr 2020, at 10:10, Stephan Ewen <[hidden email]> wrote:
>>>>
>>>> Hi all!
>>>>
>>>> I want to bring up a discussion about when we want to do the feature
>>> freeze
>>>> for 1.11.
>>>>
>>>> When kicking off the release cycle, we tentatively set the date to
>>>> end of
>>>> April, which would be in one week.
>>>>
>>>> I can say from the features I am involved with (FLIP-27, FLIP-115,
>>>> reviewing some state backend improvements, etc.) that it would be
>>>> helpful
>>>> to have two additional weeks.
>>>>
>>>> When looking at various other feature threads, my feeling is that there
>>> are
>>>> more contributors and committers that could use a few more days.
>>>> The last two months were quite exceptional in and we did lose a bit of
>>>> development speed here and there.
>>>>
>>>> How do you think about making *May 15th* the feature freeze?
>>>>
>>>> Best,
>>>> Stephan
>>>
>>>
>>

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Exact feature freeze date

Xintong Song
+1
From our side we can also benefit from the extending of feature freeze, for
pluggable slot allocation, GPU support and perjob mode on Kubernetes
deployment.

Thank you~

Xintong Song



On Thu, Apr 23, 2020 at 10:31 PM Timo Walther <[hidden email]> wrote:

>  From the SQL side, I'm sure that FLIP-95 and FLIP-105 could benefit
> from extending the feature freeze.
>
> Thanks,
> Timo
>
> On 23.04.20 16:11, Aljoscha Krettek wrote:
> > +1
> >
> > Aljoscha
> >
> > On 23.04.20 15:23, Till Rohrmann wrote:
> >> +1 for extending the feature freeze until May 15th.
> >>
> >> Cheers,
> >> Till
> >>
> >> On Thu, Apr 23, 2020 at 1:00 PM Piotr Nowojski <[hidden email]>
> >> wrote:
> >>
> >>> Hi Stephan,
> >>>
> >>> As release manager I’ve seen that quite a bit of features could use
> >>> of the
> >>> extra couple of weeks. This also includes some features that I’m
> >>> involved
> >>> with, like FLIP-76, or limiting the in-flight buffers.
> >>>
> >>> +1 From my side for extending the feature freeze until May 15th.
> >>>
> >>> Piotrek
> >>>
> >>>> On 23 Apr 2020, at 10:10, Stephan Ewen <[hidden email]> wrote:
> >>>>
> >>>> Hi all!
> >>>>
> >>>> I want to bring up a discussion about when we want to do the feature
> >>> freeze
> >>>> for 1.11.
> >>>>
> >>>> When kicking off the release cycle, we tentatively set the date to
> >>>> end of
> >>>> April, which would be in one week.
> >>>>
> >>>> I can say from the features I am involved with (FLIP-27, FLIP-115,
> >>>> reviewing some state backend improvements, etc.) that it would be
> >>>> helpful
> >>>> to have two additional weeks.
> >>>>
> >>>> When looking at various other feature threads, my feeling is that
> there
> >>> are
> >>>> more contributors and committers that could use a few more days.
> >>>> The last two months were quite exceptional in and we did lose a bit of
> >>>> development speed here and there.
> >>>>
> >>>> How do you think about making *May 15th* the feature freeze?
> >>>>
> >>>> Best,
> >>>> Stephan
> >>>
> >>>
> >>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Exact feature freeze date

Jark Wu-2
+1

Thanks,
Jark

On Thu, 23 Apr 2020 at 22:36, Xintong Song <[hidden email]> wrote:

> +1
> From our side we can also benefit from the extending of feature freeze, for
> pluggable slot allocation, GPU support and perjob mode on Kubernetes
> deployment.
>
> Thank you~
>
> Xintong Song
>
>
>
> On Thu, Apr 23, 2020 at 10:31 PM Timo Walther <[hidden email]> wrote:
>
> >  From the SQL side, I'm sure that FLIP-95 and FLIP-105 could benefit
> > from extending the feature freeze.
> >
> > Thanks,
> > Timo
> >
> > On 23.04.20 16:11, Aljoscha Krettek wrote:
> > > +1
> > >
> > > Aljoscha
> > >
> > > On 23.04.20 15:23, Till Rohrmann wrote:
> > >> +1 for extending the feature freeze until May 15th.
> > >>
> > >> Cheers,
> > >> Till
> > >>
> > >> On Thu, Apr 23, 2020 at 1:00 PM Piotr Nowojski <[hidden email]>
> > >> wrote:
> > >>
> > >>> Hi Stephan,
> > >>>
> > >>> As release manager I’ve seen that quite a bit of features could use
> > >>> of the
> > >>> extra couple of weeks. This also includes some features that I’m
> > >>> involved
> > >>> with, like FLIP-76, or limiting the in-flight buffers.
> > >>>
> > >>> +1 From my side for extending the feature freeze until May 15th.
> > >>>
> > >>> Piotrek
> > >>>
> > >>>> On 23 Apr 2020, at 10:10, Stephan Ewen <[hidden email]> wrote:
> > >>>>
> > >>>> Hi all!
> > >>>>
> > >>>> I want to bring up a discussion about when we want to do the feature
> > >>> freeze
> > >>>> for 1.11.
> > >>>>
> > >>>> When kicking off the release cycle, we tentatively set the date to
> > >>>> end of
> > >>>> April, which would be in one week.
> > >>>>
> > >>>> I can say from the features I am involved with (FLIP-27, FLIP-115,
> > >>>> reviewing some state backend improvements, etc.) that it would be
> > >>>> helpful
> > >>>> to have two additional weeks.
> > >>>>
> > >>>> When looking at various other feature threads, my feeling is that
> > there
> > >>> are
> > >>>> more contributors and committers that could use a few more days.
> > >>>> The last two months were quite exceptional in and we did lose a bit
> of
> > >>>> development speed here and there.
> > >>>>
> > >>>> How do you think about making *May 15th* the feature freeze?
> > >>>>
> > >>>> Best,
> > >>>> Stephan
> > >>>
> > >>>
> > >>
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Exact feature freeze date

Zhu Zhu
+1 for extending the code freeze date.
FLIP-119 could benefit from it.
May 15th sounds reasonable.

Thanks,
Zhu Zhu

Jark Wu <[hidden email]> 于2020年4月24日周五 上午12:01写道:

> +1
>
> Thanks,
> Jark
>
> On Thu, 23 Apr 2020 at 22:36, Xintong Song <[hidden email]> wrote:
>
> > +1
> > From our side we can also benefit from the extending of feature freeze,
> for
> > pluggable slot allocation, GPU support and perjob mode on Kubernetes
> > deployment.
> >
> > Thank you~
> >
> > Xintong Song
> >
> >
> >
> > On Thu, Apr 23, 2020 at 10:31 PM Timo Walther <[hidden email]>
> wrote:
> >
> > >  From the SQL side, I'm sure that FLIP-95 and FLIP-105 could benefit
> > > from extending the feature freeze.
> > >
> > > Thanks,
> > > Timo
> > >
> > > On 23.04.20 16:11, Aljoscha Krettek wrote:
> > > > +1
> > > >
> > > > Aljoscha
> > > >
> > > > On 23.04.20 15:23, Till Rohrmann wrote:
> > > >> +1 for extending the feature freeze until May 15th.
> > > >>
> > > >> Cheers,
> > > >> Till
> > > >>
> > > >> On Thu, Apr 23, 2020 at 1:00 PM Piotr Nowojski <[hidden email]
> >
> > > >> wrote:
> > > >>
> > > >>> Hi Stephan,
> > > >>>
> > > >>> As release manager I’ve seen that quite a bit of features could use
> > > >>> of the
> > > >>> extra couple of weeks. This also includes some features that I’m
> > > >>> involved
> > > >>> with, like FLIP-76, or limiting the in-flight buffers.
> > > >>>
> > > >>> +1 From my side for extending the feature freeze until May 15th.
> > > >>>
> > > >>> Piotrek
> > > >>>
> > > >>>> On 23 Apr 2020, at 10:10, Stephan Ewen <[hidden email]> wrote:
> > > >>>>
> > > >>>> Hi all!
> > > >>>>
> > > >>>> I want to bring up a discussion about when we want to do the
> feature
> > > >>> freeze
> > > >>>> for 1.11.
> > > >>>>
> > > >>>> When kicking off the release cycle, we tentatively set the date to
> > > >>>> end of
> > > >>>> April, which would be in one week.
> > > >>>>
> > > >>>> I can say from the features I am involved with (FLIP-27, FLIP-115,
> > > >>>> reviewing some state backend improvements, etc.) that it would be
> > > >>>> helpful
> > > >>>> to have two additional weeks.
> > > >>>>
> > > >>>> When looking at various other feature threads, my feeling is that
> > > there
> > > >>> are
> > > >>>> more contributors and committers that could use a few more days.
> > > >>>> The last two months were quite exceptional in and we did lose a
> bit
> > of
> > > >>>> development speed here and there.
> > > >>>>
> > > >>>> How do you think about making *May 15th* the feature freeze?
> > > >>>>
> > > >>>> Best,
> > > >>>> Stephan
> > > >>>
> > > >>>
> > > >>
> > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Exact feature freeze date

Jingsong Li
+1

Best,
Jingsong Lee

On Fri, Apr 24, 2020 at 2:27 AM Zhu Zhu <[hidden email]> wrote:

> +1 for extending the code freeze date.
> FLIP-119 could benefit from it.
> May 15th sounds reasonable.
>
> Thanks,
> Zhu Zhu
>
> Jark Wu <[hidden email]> 于2020年4月24日周五 上午12:01写道:
>
> > +1
> >
> > Thanks,
> > Jark
> >
> > On Thu, 23 Apr 2020 at 22:36, Xintong Song <[hidden email]>
> wrote:
> >
> > > +1
> > > From our side we can also benefit from the extending of feature freeze,
> > for
> > > pluggable slot allocation, GPU support and perjob mode on Kubernetes
> > > deployment.
> > >
> > > Thank you~
> > >
> > > Xintong Song
> > >
> > >
> > >
> > > On Thu, Apr 23, 2020 at 10:31 PM Timo Walther <[hidden email]>
> > wrote:
> > >
> > > >  From the SQL side, I'm sure that FLIP-95 and FLIP-105 could benefit
> > > > from extending the feature freeze.
> > > >
> > > > Thanks,
> > > > Timo
> > > >
> > > > On 23.04.20 16:11, Aljoscha Krettek wrote:
> > > > > +1
> > > > >
> > > > > Aljoscha
> > > > >
> > > > > On 23.04.20 15:23, Till Rohrmann wrote:
> > > > >> +1 for extending the feature freeze until May 15th.
> > > > >>
> > > > >> Cheers,
> > > > >> Till
> > > > >>
> > > > >> On Thu, Apr 23, 2020 at 1:00 PM Piotr Nowojski <
> [hidden email]
> > >
> > > > >> wrote:
> > > > >>
> > > > >>> Hi Stephan,
> > > > >>>
> > > > >>> As release manager I’ve seen that quite a bit of features could
> use
> > > > >>> of the
> > > > >>> extra couple of weeks. This also includes some features that I’m
> > > > >>> involved
> > > > >>> with, like FLIP-76, or limiting the in-flight buffers.
> > > > >>>
> > > > >>> +1 From my side for extending the feature freeze until May 15th.
> > > > >>>
> > > > >>> Piotrek
> > > > >>>
> > > > >>>> On 23 Apr 2020, at 10:10, Stephan Ewen <[hidden email]>
> wrote:
> > > > >>>>
> > > > >>>> Hi all!
> > > > >>>>
> > > > >>>> I want to bring up a discussion about when we want to do the
> > feature
> > > > >>> freeze
> > > > >>>> for 1.11.
> > > > >>>>
> > > > >>>> When kicking off the release cycle, we tentatively set the date
> to
> > > > >>>> end of
> > > > >>>> April, which would be in one week.
> > > > >>>>
> > > > >>>> I can say from the features I am involved with (FLIP-27,
> FLIP-115,
> > > > >>>> reviewing some state backend improvements, etc.) that it would
> be
> > > > >>>> helpful
> > > > >>>> to have two additional weeks.
> > > > >>>>
> > > > >>>> When looking at various other feature threads, my feeling is
> that
> > > > there
> > > > >>> are
> > > > >>>> more contributors and committers that could use a few more days.
> > > > >>>> The last two months were quite exceptional in and we did lose a
> > bit
> > > of
> > > > >>>> development speed here and there.
> > > > >>>>
> > > > >>>> How do you think about making *May 15th* the feature freeze?
> > > > >>>>
> > > > >>>> Best,
> > > > >>>> Stephan
> > > > >>>
> > > > >>>
> > > > >>
> > > >
> > > >
> > >
> >
>


--
Best, Jingsong Lee
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Exact feature freeze date

Leonard Xu
 + 1 for the feature freeze date

Best,
Leonard Xu


> 在 2020年4月24日,09:32,Jingsong Li <[hidden email]> 写道:
>
> +1
>
> Best,
> Jingsong Lee
>
> On Fri, Apr 24, 2020 at 2:27 AM Zhu Zhu <[hidden email]> wrote:
>
>> +1 for extending the code freeze date.
>> FLIP-119 could benefit from it.
>> May 15th sounds reasonable.
>>
>> Thanks,
>> Zhu Zhu
>>
>> Jark Wu <[hidden email]> 于2020年4月24日周五 上午12:01写道:
>>
>>> +1
>>>
>>> Thanks,
>>> Jark
>>>
>>> On Thu, 23 Apr 2020 at 22:36, Xintong Song <[hidden email]>
>> wrote:
>>>
>>>> +1
>>>> From our side we can also benefit from the extending of feature freeze,
>>> for
>>>> pluggable slot allocation, GPU support and perjob mode on Kubernetes
>>>> deployment.
>>>>
>>>> Thank you~
>>>>
>>>> Xintong Song
>>>>
>>>>
>>>>
>>>> On Thu, Apr 23, 2020 at 10:31 PM Timo Walther <[hidden email]>
>>> wrote:
>>>>
>>>>> From the SQL side, I'm sure that FLIP-95 and FLIP-105 could benefit
>>>>> from extending the feature freeze.
>>>>>
>>>>> Thanks,
>>>>> Timo
>>>>>
>>>>> On 23.04.20 16:11, Aljoscha Krettek wrote:
>>>>>> +1
>>>>>>
>>>>>> Aljoscha
>>>>>>
>>>>>> On 23.04.20 15:23, Till Rohrmann wrote:
>>>>>>> +1 for extending the feature freeze until May 15th.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Till
>>>>>>>
>>>>>>> On Thu, Apr 23, 2020 at 1:00 PM Piotr Nowojski <
>> [hidden email]
>>>>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Stephan,
>>>>>>>>
>>>>>>>> As release manager I’ve seen that quite a bit of features could
>> use
>>>>>>>> of the
>>>>>>>> extra couple of weeks. This also includes some features that I’m
>>>>>>>> involved
>>>>>>>> with, like FLIP-76, or limiting the in-flight buffers.
>>>>>>>>
>>>>>>>> +1 From my side for extending the feature freeze until May 15th.
>>>>>>>>
>>>>>>>> Piotrek
>>>>>>>>
>>>>>>>>> On 23 Apr 2020, at 10:10, Stephan Ewen <[hidden email]>
>> wrote:
>>>>>>>>>
>>>>>>>>> Hi all!
>>>>>>>>>
>>>>>>>>> I want to bring up a discussion about when we want to do the
>>> feature
>>>>>>>> freeze
>>>>>>>>> for 1.11.
>>>>>>>>>
>>>>>>>>> When kicking off the release cycle, we tentatively set the date
>> to
>>>>>>>>> end of
>>>>>>>>> April, which would be in one week.
>>>>>>>>>
>>>>>>>>> I can say from the features I am involved with (FLIP-27,
>> FLIP-115,
>>>>>>>>> reviewing some state backend improvements, etc.) that it would
>> be
>>>>>>>>> helpful
>>>>>>>>> to have two additional weeks.
>>>>>>>>>
>>>>>>>>> When looking at various other feature threads, my feeling is
>> that
>>>>> there
>>>>>>>> are
>>>>>>>>> more contributors and committers that could use a few more days.
>>>>>>>>> The last two months were quite exceptional in and we did lose a
>>> bit
>>>> of
>>>>>>>>> development speed here and there.
>>>>>>>>>
>>>>>>>>> How do you think about making *May 15th* the feature freeze?
>>>>>>>>>
>>>>>>>>> Best,
>>>>>>>>> Stephan
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
>
> --
> Best, Jingsong Lee

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Exact feature freeze date

Dian Fu-2
+1

Regards,
Dian

> 在 2020年4月24日,上午9:47,Leonard Xu <[hidden email]> 写道:
>
> + 1 for the feature freeze date
>
> Best,
> Leonard Xu
>
>
>> 在 2020年4月24日,09:32,Jingsong Li <[hidden email]> 写道:
>>
>> +1
>>
>> Best,
>> Jingsong Lee
>>
>> On Fri, Apr 24, 2020 at 2:27 AM Zhu Zhu <[hidden email]> wrote:
>>
>>> +1 for extending the code freeze date.
>>> FLIP-119 could benefit from it.
>>> May 15th sounds reasonable.
>>>
>>> Thanks,
>>> Zhu Zhu
>>>
>>> Jark Wu <[hidden email]> 于2020年4月24日周五 上午12:01写道:
>>>
>>>> +1
>>>>
>>>> Thanks,
>>>> Jark
>>>>
>>>> On Thu, 23 Apr 2020 at 22:36, Xintong Song <[hidden email]>
>>> wrote:
>>>>
>>>>> +1
>>>>> From our side we can also benefit from the extending of feature freeze,
>>>> for
>>>>> pluggable slot allocation, GPU support and perjob mode on Kubernetes
>>>>> deployment.
>>>>>
>>>>> Thank you~
>>>>>
>>>>> Xintong Song
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Apr 23, 2020 at 10:31 PM Timo Walther <[hidden email]>
>>>> wrote:
>>>>>
>>>>>> From the SQL side, I'm sure that FLIP-95 and FLIP-105 could benefit
>>>>>> from extending the feature freeze.
>>>>>>
>>>>>> Thanks,
>>>>>> Timo
>>>>>>
>>>>>> On 23.04.20 16:11, Aljoscha Krettek wrote:
>>>>>>> +1
>>>>>>>
>>>>>>> Aljoscha
>>>>>>>
>>>>>>> On 23.04.20 15:23, Till Rohrmann wrote:
>>>>>>>> +1 for extending the feature freeze until May 15th.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Till
>>>>>>>>
>>>>>>>> On Thu, Apr 23, 2020 at 1:00 PM Piotr Nowojski <
>>> [hidden email]
>>>>>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi Stephan,
>>>>>>>>>
>>>>>>>>> As release manager I’ve seen that quite a bit of features could
>>> use
>>>>>>>>> of the
>>>>>>>>> extra couple of weeks. This also includes some features that I’m
>>>>>>>>> involved
>>>>>>>>> with, like FLIP-76, or limiting the in-flight buffers.
>>>>>>>>>
>>>>>>>>> +1 From my side for extending the feature freeze until May 15th.
>>>>>>>>>
>>>>>>>>> Piotrek
>>>>>>>>>
>>>>>>>>>> On 23 Apr 2020, at 10:10, Stephan Ewen <[hidden email]>
>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi all!
>>>>>>>>>>
>>>>>>>>>> I want to bring up a discussion about when we want to do the
>>>> feature
>>>>>>>>> freeze
>>>>>>>>>> for 1.11.
>>>>>>>>>>
>>>>>>>>>> When kicking off the release cycle, we tentatively set the date
>>> to
>>>>>>>>>> end of
>>>>>>>>>> April, which would be in one week.
>>>>>>>>>>
>>>>>>>>>> I can say from the features I am involved with (FLIP-27,
>>> FLIP-115,
>>>>>>>>>> reviewing some state backend improvements, etc.) that it would
>>> be
>>>>>>>>>> helpful
>>>>>>>>>> to have two additional weeks.
>>>>>>>>>>
>>>>>>>>>> When looking at various other feature threads, my feeling is
>>> that
>>>>>> there
>>>>>>>>> are
>>>>>>>>>> more contributors and committers that could use a few more days.
>>>>>>>>>> The last two months were quite exceptional in and we did lose a
>>>> bit
>>>>> of
>>>>>>>>>> development speed here and there.
>>>>>>>>>>
>>>>>>>>>> How do you think about making *May 15th* the feature freeze?
>>>>>>>>>>
>>>>>>>>>> Best,
>>>>>>>>>> Stephan
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>>
>> --
>> Best, Jingsong Lee
>

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Exact feature freeze date

Yangze Guo
+1

Best,
Yangze Guo

On Fri, Apr 24, 2020 at 9:49 AM Dian Fu <[hidden email]> wrote:

>
> +1
>
> Regards,
> Dian
>
> > 在 2020年4月24日,上午9:47,Leonard Xu <[hidden email]> 写道:
> >
> > + 1 for the feature freeze date
> >
> > Best,
> > Leonard Xu
> >
> >
> >> 在 2020年4月24日,09:32,Jingsong Li <[hidden email]> 写道:
> >>
> >> +1
> >>
> >> Best,
> >> Jingsong Lee
> >>
> >> On Fri, Apr 24, 2020 at 2:27 AM Zhu Zhu <[hidden email]> wrote:
> >>
> >>> +1 for extending the code freeze date.
> >>> FLIP-119 could benefit from it.
> >>> May 15th sounds reasonable.
> >>>
> >>> Thanks,
> >>> Zhu Zhu
> >>>
> >>> Jark Wu <[hidden email]> 于2020年4月24日周五 上午12:01写道:
> >>>
> >>>> +1
> >>>>
> >>>> Thanks,
> >>>> Jark
> >>>>
> >>>> On Thu, 23 Apr 2020 at 22:36, Xintong Song <[hidden email]>
> >>> wrote:
> >>>>
> >>>>> +1
> >>>>> From our side we can also benefit from the extending of feature freeze,
> >>>> for
> >>>>> pluggable slot allocation, GPU support and perjob mode on Kubernetes
> >>>>> deployment.
> >>>>>
> >>>>> Thank you~
> >>>>>
> >>>>> Xintong Song
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Thu, Apr 23, 2020 at 10:31 PM Timo Walther <[hidden email]>
> >>>> wrote:
> >>>>>
> >>>>>> From the SQL side, I'm sure that FLIP-95 and FLIP-105 could benefit
> >>>>>> from extending the feature freeze.
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Timo
> >>>>>>
> >>>>>> On 23.04.20 16:11, Aljoscha Krettek wrote:
> >>>>>>> +1
> >>>>>>>
> >>>>>>> Aljoscha
> >>>>>>>
> >>>>>>> On 23.04.20 15:23, Till Rohrmann wrote:
> >>>>>>>> +1 for extending the feature freeze until May 15th.
> >>>>>>>>
> >>>>>>>> Cheers,
> >>>>>>>> Till
> >>>>>>>>
> >>>>>>>> On Thu, Apr 23, 2020 at 1:00 PM Piotr Nowojski <
> >>> [hidden email]
> >>>>>
> >>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> Hi Stephan,
> >>>>>>>>>
> >>>>>>>>> As release manager I’ve seen that quite a bit of features could
> >>> use
> >>>>>>>>> of the
> >>>>>>>>> extra couple of weeks. This also includes some features that I’m
> >>>>>>>>> involved
> >>>>>>>>> with, like FLIP-76, or limiting the in-flight buffers.
> >>>>>>>>>
> >>>>>>>>> +1 From my side for extending the feature freeze until May 15th.
> >>>>>>>>>
> >>>>>>>>> Piotrek
> >>>>>>>>>
> >>>>>>>>>> On 23 Apr 2020, at 10:10, Stephan Ewen <[hidden email]>
> >>> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Hi all!
> >>>>>>>>>>
> >>>>>>>>>> I want to bring up a discussion about when we want to do the
> >>>> feature
> >>>>>>>>> freeze
> >>>>>>>>>> for 1.11.
> >>>>>>>>>>
> >>>>>>>>>> When kicking off the release cycle, we tentatively set the date
> >>> to
> >>>>>>>>>> end of
> >>>>>>>>>> April, which would be in one week.
> >>>>>>>>>>
> >>>>>>>>>> I can say from the features I am involved with (FLIP-27,
> >>> FLIP-115,
> >>>>>>>>>> reviewing some state backend improvements, etc.) that it would
> >>> be
> >>>>>>>>>> helpful
> >>>>>>>>>> to have two additional weeks.
> >>>>>>>>>>
> >>>>>>>>>> When looking at various other feature threads, my feeling is
> >>> that
> >>>>>> there
> >>>>>>>>> are
> >>>>>>>>>> more contributors and committers that could use a few more days.
> >>>>>>>>>> The last two months were quite exceptional in and we did lose a
> >>>> bit
> >>>>> of
> >>>>>>>>>> development speed here and there.
> >>>>>>>>>>
> >>>>>>>>>> How do you think about making *May 15th* the feature freeze?
> >>>>>>>>>>
> >>>>>>>>>> Best,
> >>>>>>>>>> Stephan
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >>
> >> --
> >> Best, Jingsong Lee
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Exact feature freeze date

Danny Chan
+1 for extending the feature freeze until May 15th.

Best,
Danny Chan
在 2020年4月24日 +0800 AM9:51,Yangze Guo <[hidden email]>,写道:

> +1
>
> Best,
> Yangze Guo
>
> On Fri, Apr 24, 2020 at 9:49 AM Dian Fu <[hidden email]> wrote:
> >
> > +1
> >
> > Regards,
> > Dian
> >
> > > 在 2020年4月24日,上午9:47,Leonard Xu <[hidden email]> 写道:
> > >
> > > + 1 for the feature freeze date
> > >
> > > Best,
> > > Leonard Xu
> > >
> > >
> > > > 在 2020年4月24日,09:32,Jingsong Li <[hidden email]> 写道:
> > > >
> > > > +1
> > > >
> > > > Best,
> > > > Jingsong Lee
> > > >
> > > > On Fri, Apr 24, 2020 at 2:27 AM Zhu Zhu <[hidden email]> wrote:
> > > >
> > > > > +1 for extending the code freeze date.
> > > > > FLIP-119 could benefit from it.
> > > > > May 15th sounds reasonable.
> > > > >
> > > > > Thanks,
> > > > > Zhu Zhu
> > > > >
> > > > > Jark Wu <[hidden email]> 于2020年4月24日周五 上午12:01写道:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > Thanks,
> > > > > > Jark
> > > > > >
> > > > > > On Thu, 23 Apr 2020 at 22:36, Xintong Song <[hidden email]>
> > > > > wrote:
> > > > > >
> > > > > > > +1
> > > > > > > From our side we can also benefit from the extending of feature freeze,
> > > > > > for
> > > > > > > pluggable slot allocation, GPU support and perjob mode on Kubernetes
> > > > > > > deployment.
> > > > > > >
> > > > > > > Thank you~
> > > > > > >
> > > > > > > Xintong Song
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Apr 23, 2020 at 10:31 PM Timo Walther <[hidden email]>
> > > > > > wrote:
> > > > > > >
> > > > > > > > From the SQL side, I'm sure that FLIP-95 and FLIP-105 could benefit
> > > > > > > > from extending the feature freeze.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Timo
> > > > > > > >
> > > > > > > > On 23.04.20 16:11, Aljoscha Krettek wrote:
> > > > > > > > > +1
> > > > > > > > >
> > > > > > > > > Aljoscha
> > > > > > > > >
> > > > > > > > > On 23.04.20 15:23, Till Rohrmann wrote:
> > > > > > > > > > +1 for extending the feature freeze until May 15th.
> > > > > > > > > >
> > > > > > > > > > Cheers,
> > > > > > > > > > Till
> > > > > > > > > >
> > > > > > > > > > On Thu, Apr 23, 2020 at 1:00 PM Piotr Nowojski <
> > > > > [hidden email]
> > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Hi Stephan,
> > > > > > > > > > >
> > > > > > > > > > > As release manager I’ve seen that quite a bit of features could
> > > > > use
> > > > > > > > > > > of the
> > > > > > > > > > > extra couple of weeks. This also includes some features that I’m
> > > > > > > > > > > involved
> > > > > > > > > > > with, like FLIP-76, or limiting the in-flight buffers.
> > > > > > > > > > >
> > > > > > > > > > > +1 From my side for extending the feature freeze until May 15th.
> > > > > > > > > > >
> > > > > > > > > > > Piotrek
> > > > > > > > > > >
> > > > > > > > > > > > On 23 Apr 2020, at 10:10, Stephan Ewen <[hidden email]>
> > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > Hi all!
> > > > > > > > > > > >
> > > > > > > > > > > > I want to bring up a discussion about when we want to do the
> > > > > > feature
> > > > > > > > > > > freeze
> > > > > > > > > > > > for 1.11.
> > > > > > > > > > > >
> > > > > > > > > > > > When kicking off the release cycle, we tentatively set the date
> > > > > to
> > > > > > > > > > > > end of
> > > > > > > > > > > > April, which would be in one week.
> > > > > > > > > > > >
> > > > > > > > > > > > I can say from the features I am involved with (FLIP-27,
> > > > > FLIP-115,
> > > > > > > > > > > > reviewing some state backend improvements, etc.) that it would
> > > > > be
> > > > > > > > > > > > helpful
> > > > > > > > > > > > to have two additional weeks.
> > > > > > > > > > > >
> > > > > > > > > > > > When looking at various other feature threads, my feeling is
> > > > > that
> > > > > > > > there
> > > > > > > > > > > are
> > > > > > > > > > > > more contributors and committers that could use a few more days.
> > > > > > > > > > > > The last two months were quite exceptional in and we did lose a
> > > > > > bit
> > > > > > > of
> > > > > > > > > > > > development speed here and there.
> > > > > > > > > > > >
> > > > > > > > > > > > How do you think about making *May 15th* the feature freeze?
> > > > > > > > > > > >
> > > > > > > > > > > > Best,
> > > > > > > > > > > > Stephan
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Best, Jingsong Lee
> > >
> >
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Exact feature freeze date

Zhijiang(wangzhijiang999)
+1 for extending the feature freeze until May 15th.

Best,
Zhijiang


------------------------------------------------------------------
From:Danny Chan <[hidden email]>
Send Time:2020 Apr. 24 (Fri.) 10:51
To:dev <[hidden email]>
Subject:Re: [DISCUSS] Exact feature freeze date

+1 for extending the feature freeze until May 15th.

Best,
Danny Chan
在 2020年4月24日 +0800 AM9:51,Yangze Guo <[hidden email]>,写道:

> +1
>
> Best,
> Yangze Guo
>
> On Fri, Apr 24, 2020 at 9:49 AM Dian Fu <[hidden email]> wrote:
> >
> > +1
> >
> > Regards,
> > Dian
> >
> > > 在 2020年4月24日,上午9:47,Leonard Xu <[hidden email]> 写道:
> > >
> > > + 1 for the feature freeze date
> > >
> > > Best,
> > > Leonard Xu
> > >
> > >
> > > > 在 2020年4月24日,09:32,Jingsong Li <[hidden email]> 写道:
> > > >
> > > > +1
> > > >
> > > > Best,
> > > > Jingsong Lee
> > > >
> > > > On Fri, Apr 24, 2020 at 2:27 AM Zhu Zhu <[hidden email]> wrote:
> > > >
> > > > > +1 for extending the code freeze date.
> > > > > FLIP-119 could benefit from it.
> > > > > May 15th sounds reasonable.
> > > > >
> > > > > Thanks,
> > > > > Zhu Zhu
> > > > >
> > > > > Jark Wu <[hidden email]> 于2020年4月24日周五 上午12:01写道:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > Thanks,
> > > > > > Jark
> > > > > >
> > > > > > On Thu, 23 Apr 2020 at 22:36, Xintong Song <[hidden email]>
> > > > > wrote:
> > > > > >
> > > > > > > +1
> > > > > > > From our side we can also benefit from the extending of feature freeze,
> > > > > > for
> > > > > > > pluggable slot allocation, GPU support and perjob mode on Kubernetes
> > > > > > > deployment.
> > > > > > >
> > > > > > > Thank you~
> > > > > > >
> > > > > > > Xintong Song
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Apr 23, 2020 at 10:31 PM Timo Walther <[hidden email]>
> > > > > > wrote:
> > > > > > >
> > > > > > > > From the SQL side, I'm sure that FLIP-95 and FLIP-105 could benefit
> > > > > > > > from extending the feature freeze.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Timo
> > > > > > > >
> > > > > > > > On 23.04.20 16:11, Aljoscha Krettek wrote:
> > > > > > > > > +1
> > > > > > > > >
> > > > > > > > > Aljoscha
> > > > > > > > >
> > > > > > > > > On 23.04.20 15:23, Till Rohrmann wrote:
> > > > > > > > > > +1 for extending the feature freeze until May 15th.
> > > > > > > > > >
> > > > > > > > > > Cheers,
> > > > > > > > > > Till
> > > > > > > > > >
> > > > > > > > > > On Thu, Apr 23, 2020 at 1:00 PM Piotr Nowojski <
> > > > > [hidden email]
> > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Hi Stephan,
> > > > > > > > > > >
> > > > > > > > > > > As release manager I’ve seen that quite a bit of features could
> > > > > use
> > > > > > > > > > > of the
> > > > > > > > > > > extra couple of weeks. This also includes some features that I’m
> > > > > > > > > > > involved
> > > > > > > > > > > with, like FLIP-76, or limiting the in-flight buffers.
> > > > > > > > > > >
> > > > > > > > > > > +1 From my side for extending the feature freeze until May 15th.
> > > > > > > > > > >
> > > > > > > > > > > Piotrek
> > > > > > > > > > >
> > > > > > > > > > > > On 23 Apr 2020, at 10:10, Stephan Ewen <[hidden email]>
> > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > Hi all!
> > > > > > > > > > > >
> > > > > > > > > > > > I want to bring up a discussion about when we want to do the
> > > > > > feature
> > > > > > > > > > > freeze
> > > > > > > > > > > > for 1.11.
> > > > > > > > > > > >
> > > > > > > > > > > > When kicking off the release cycle, we tentatively set the date
> > > > > to
> > > > > > > > > > > > end of
> > > > > > > > > > > > April, which would be in one week.
> > > > > > > > > > > >
> > > > > > > > > > > > I can say from the features I am involved with (FLIP-27,
> > > > > FLIP-115,
> > > > > > > > > > > > reviewing some state backend improvements, etc.) that it would
> > > > > be
> > > > > > > > > > > > helpful
> > > > > > > > > > > > to have two additional weeks.
> > > > > > > > > > > >
> > > > > > > > > > > > When looking at various other feature threads, my feeling is
> > > > > that
> > > > > > > > there
> > > > > > > > > > > are
> > > > > > > > > > > > more contributors and committers that could use a few more days.
> > > > > > > > > > > > The last two months were quite exceptional in and we did lose a
> > > > > > bit
> > > > > > > of
> > > > > > > > > > > > development speed here and there.
> > > > > > > > > > > >
> > > > > > > > > > > > How do you think about making *May 15th* the feature freeze?
> > > > > > > > > > > >
> > > > > > > > > > > > Best,
> > > > > > > > > > > > Stephan
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Best, Jingsong Lee
> > >
> >

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Exact feature freeze date

curcur
In reply to this post by Stephan Ewen
+1

On Thu, Apr 23, 2020 at 4:10 PM Stephan Ewen <[hidden email]> wrote:

> Hi all!
>
> I want to bring up a discussion about when we want to do the feature freeze
> for 1.11.
>
> When kicking off the release cycle, we tentatively set the date to end of
> April, which would be in one week.
>
> I can say from the features I am involved with (FLIP-27, FLIP-115,
> reviewing some state backend improvements, etc.) that it would be helpful
> to have two additional weeks.
>
> When looking at various other feature threads, my feeling is that there are
> more contributors and committers that could use a few more days.
> The last two months were quite exceptional in and we did lose a bit of
> development speed here and there.
>
> How do you think about making *May 15th* the feature freeze?
>
> Best,
> Stephan
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Exact feature freeze date

Yu Li
+1 for extending the feature freeze to May 15th.

Best Regards,
Yu


On Fri, 24 Apr 2020 at 14:43, Yuan Mei <[hidden email]> wrote:

> +1
>
> On Thu, Apr 23, 2020 at 4:10 PM Stephan Ewen <[hidden email]> wrote:
>
> > Hi all!
> >
> > I want to bring up a discussion about when we want to do the feature
> freeze
> > for 1.11.
> >
> > When kicking off the release cycle, we tentatively set the date to end of
> > April, which would be in one week.
> >
> > I can say from the features I am involved with (FLIP-27, FLIP-115,
> > reviewing some state backend improvements, etc.) that it would be helpful
> > to have two additional weeks.
> >
> > When looking at various other feature threads, my feeling is that there
> are
> > more contributors and committers that could use a few more days.
> > The last two months were quite exceptional in and we did lose a bit of
> > development speed here and there.
> >
> > How do you think about making *May 15th* the feature freeze?
> >
> > Best,
> > Stephan
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Exact feature freeze date

Piotr Nowojski-3
Hi,

Couple of contributors asked for extending cutting the release branch until Monday, what do you think about such extension?

(+1 from my side)

Piotrek

> On 25 Apr 2020, at 21:24, Yu Li <[hidden email]> wrote:
>
> +1 for extending the feature freeze to May 15th.
>
> Best Regards,
> Yu
>
>
> On Fri, 24 Apr 2020 at 14:43, Yuan Mei <[hidden email]> wrote:
>
>> +1
>>
>> On Thu, Apr 23, 2020 at 4:10 PM Stephan Ewen <[hidden email]> wrote:
>>
>>> Hi all!
>>>
>>> I want to bring up a discussion about when we want to do the feature
>> freeze
>>> for 1.11.
>>>
>>> When kicking off the release cycle, we tentatively set the date to end of
>>> April, which would be in one week.
>>>
>>> I can say from the features I am involved with (FLIP-27, FLIP-115,
>>> reviewing some state backend improvements, etc.) that it would be helpful
>>> to have two additional weeks.
>>>
>>> When looking at various other feature threads, my feeling is that there
>> are
>>> more contributors and committers that could use a few more days.
>>> The last two months were quite exceptional in and we did lose a bit of
>>> development speed here and there.
>>>
>>> How do you think about making *May 15th* the feature freeze?
>>>
>>> Best,
>>> Stephan
>>>
>>

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Exact feature freeze date

Robert Metzger
I'm okay, but I would suggest to agree on a time of day. What about Monday
morning in Europe?

On Fri, May 15, 2020 at 1:43 PM Piotr Nowojski <[hidden email]> wrote:

> Hi,
>
> Couple of contributors asked for extending cutting the release branch
> until Monday, what do you think about such extension?
>
> (+1 from my side)
>
> Piotrek
>
> > On 25 Apr 2020, at 21:24, Yu Li <[hidden email]> wrote:
> >
> > +1 for extending the feature freeze to May 15th.
> >
> > Best Regards,
> > Yu
> >
> >
> > On Fri, 24 Apr 2020 at 14:43, Yuan Mei <[hidden email]> wrote:
> >
> >> +1
> >>
> >> On Thu, Apr 23, 2020 at 4:10 PM Stephan Ewen <[hidden email]> wrote:
> >>
> >>> Hi all!
> >>>
> >>> I want to bring up a discussion about when we want to do the feature
> >> freeze
> >>> for 1.11.
> >>>
> >>> When kicking off the release cycle, we tentatively set the date to end
> of
> >>> April, which would be in one week.
> >>>
> >>> I can say from the features I am involved with (FLIP-27, FLIP-115,
> >>> reviewing some state backend improvements, etc.) that it would be
> helpful
> >>> to have two additional weeks.
> >>>
> >>> When looking at various other feature threads, my feeling is that there
> >> are
> >>> more contributors and committers that could use a few more days.
> >>> The last two months were quite exceptional in and we did lose a bit of
> >>> development speed here and there.
> >>>
> >>> How do you think about making *May 15th* the feature freeze?
> >>>
> >>> Best,
> >>> Stephan
> >>>
> >>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Exact feature freeze date

Till Rohrmann
+1 from my side extend the feature freeze until Monday morning.

Cheers,
Till

On Fri, May 15, 2020 at 2:04 PM Robert Metzger <[hidden email]> wrote:

> I'm okay, but I would suggest to agree on a time of day. What about Monday
> morning in Europe?
>
> On Fri, May 15, 2020 at 1:43 PM Piotr Nowojski <[hidden email]>
> wrote:
>
> > Hi,
> >
> > Couple of contributors asked for extending cutting the release branch
> > until Monday, what do you think about such extension?
> >
> > (+1 from my side)
> >
> > Piotrek
> >
> > > On 25 Apr 2020, at 21:24, Yu Li <[hidden email]> wrote:
> > >
> > > +1 for extending the feature freeze to May 15th.
> > >
> > > Best Regards,
> > > Yu
> > >
> > >
> > > On Fri, 24 Apr 2020 at 14:43, Yuan Mei <[hidden email]> wrote:
> > >
> > >> +1
> > >>
> > >> On Thu, Apr 23, 2020 at 4:10 PM Stephan Ewen <[hidden email]>
> wrote:
> > >>
> > >>> Hi all!
> > >>>
> > >>> I want to bring up a discussion about when we want to do the feature
> > >> freeze
> > >>> for 1.11.
> > >>>
> > >>> When kicking off the release cycle, we tentatively set the date to
> end
> > of
> > >>> April, which would be in one week.
> > >>>
> > >>> I can say from the features I am involved with (FLIP-27, FLIP-115,
> > >>> reviewing some state backend improvements, etc.) that it would be
> > helpful
> > >>> to have two additional weeks.
> > >>>
> > >>> When looking at various other feature threads, my feeling is that
> there
> > >> are
> > >>> more contributors and committers that could use a few more days.
> > >>> The last two months were quite exceptional in and we did lose a bit
> of
> > >>> development speed here and there.
> > >>>
> > >>> How do you think about making *May 15th* the feature freeze?
> > >>>
> > >>> Best,
> > >>> Stephan
> > >>>
> > >>
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Exact feature freeze date

Jingsong Li
+1 for Monday morning.

Best,
Jingsong Lee

On Fri, May 15, 2020 at 8:45 PM Till Rohrmann <[hidden email]> wrote:

> +1 from my side extend the feature freeze until Monday morning.
>
> Cheers,
> Till
>
> On Fri, May 15, 2020 at 2:04 PM Robert Metzger <[hidden email]>
> wrote:
>
> > I'm okay, but I would suggest to agree on a time of day. What about
> Monday
> > morning in Europe?
> >
> > On Fri, May 15, 2020 at 1:43 PM Piotr Nowojski <[hidden email]>
> > wrote:
> >
> > > Hi,
> > >
> > > Couple of contributors asked for extending cutting the release branch
> > > until Monday, what do you think about such extension?
> > >
> > > (+1 from my side)
> > >
> > > Piotrek
> > >
> > > > On 25 Apr 2020, at 21:24, Yu Li <[hidden email]> wrote:
> > > >
> > > > +1 for extending the feature freeze to May 15th.
> > > >
> > > > Best Regards,
> > > > Yu
> > > >
> > > >
> > > > On Fri, 24 Apr 2020 at 14:43, Yuan Mei <[hidden email]>
> wrote:
> > > >
> > > >> +1
> > > >>
> > > >> On Thu, Apr 23, 2020 at 4:10 PM Stephan Ewen <[hidden email]>
> > wrote:
> > > >>
> > > >>> Hi all!
> > > >>>
> > > >>> I want to bring up a discussion about when we want to do the
> feature
> > > >> freeze
> > > >>> for 1.11.
> > > >>>
> > > >>> When kicking off the release cycle, we tentatively set the date to
> > end
> > > of
> > > >>> April, which would be in one week.
> > > >>>
> > > >>> I can say from the features I am involved with (FLIP-27, FLIP-115,
> > > >>> reviewing some state backend improvements, etc.) that it would be
> > > helpful
> > > >>> to have two additional weeks.
> > > >>>
> > > >>> When looking at various other feature threads, my feeling is that
> > there
> > > >> are
> > > >>> more contributors and committers that could use a few more days.
> > > >>> The last two months were quite exceptional in and we did lose a bit
> > of
> > > >>> development speed here and there.
> > > >>>
> > > >>> How do you think about making *May 15th* the feature freeze?
> > > >>>
> > > >>> Best,
> > > >>> Stephan
> > > >>>
> > > >>
> > >
> > >
> >
>


--
Best, Jingsong Lee
12