+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 <twal...@apache.org> 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 <pi...@ververica.com> > >> 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 <se...@apache.org> 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 > >>> > >>> > >> > >
