+1 to extend the feature freeze date to Feb. 14th, which might be a good
Valentine's Day present for all Flink developers as well (smile).

Best Regards,
Yu


On Wed, 26 Jan 2022 at 14:50, Yuan Mei <yuanmei.w...@gmail.com> wrote:

> +1 extending feature freeze for one week.
>
> Code Freeze on 6th (end of Spring Festival) is equivalent to say code
> freeze at the end of this week for Chinese buddies, since Spring Festival
> starts next week.
> It also means they should be partially available during the holiday,
> otherwise they would block the release if any unexpected issues arise.
>
> The situation sounds a bit stressed and can be resolved very well by
> extending the freeze date for a bit.
>
> Best
> Yuan
>
> On Wed, Jan 26, 2022 at 11:18 AM Yun Tang <myas...@live.com> wrote:
>
> > Since the official Spring Festival holidays in China starts from Jan 31th
> > to Feb 6th, and many developers in China would enjoy the holidays at that
> > time.
> > +1 for extending the feature freeze.
> >
> > Best
> > Yun Tang
> > ________________________________
> > From: Jingsong Li <jingsongl...@gmail.com>
> > Sent: Wednesday, January 26, 2022 10:32
> > To: dev <dev@flink.apache.org>
> > Subject: Re: [DISCUSS] Pushing Apache Flink 1.15 Feature Freeze
> >
> > +1 for extending the feature freeze.
> >
> > Thanks Joe for driving.
> >
> > Best,
> > Jingsong
> >
> > On Wed, Jan 26, 2022 at 12:04 AM Martijn Visser <mart...@ververica.com>
> > wrote:
> > >
> > > Hi all,
> > >
> > > +1 for extending the feature freeze. We could use the time to try to
> wrap
> > > up some important SQL related features and improvements.
> > >
> > > Best regards,
> > >
> > > Martijn
> > >
> > > On Tue, 25 Jan 2022 at 16:38, Johannes Moser <j...@ververica.com>
> wrote:
> > >
> > > > Dear Flink community,
> > > >
> > > > as mentioned in the summary mail earlier some contributors voiced
> that
> > > > they would benefit from pushing the feature freeze for 1.15. by a
> week.
> > > > This would mean Monday, 14th of February 2022, end of business CEST.
> > > >
> > > > Please let us know in case you got any concerns.
> > > >
> > > >
> > > > Best,
> > > > Till, Yun Gao & Joe
> >
>

Reply via email to