[DISCUSS] 1.12 feature freeze date += one week ?

[Stephan Ewen <se...@apache.org>]

Hi all!

We are approaching the feature freeze date for the 1.12 release that was
discussed earlier.

From my side and the developments I am involved with, we are close and in
good shape, but could really use one more week to round things off. It
would help both the code quality and our mental health a lot :-)

From some personal conversations I heard at least from some other
committers a similar sentiment.

My proposal would hence be to set the 1.12 cutoff date to the weekend of
the 7th/8th and fork the release-1.12 branch on Monday Nov. 9th.

What do you think?

Best,
Stephan

Re: [DISCUSS] 1.12 feature freeze date += one week ?

[Stephan Ewen <se...@apache.org>]

Thanks, Robert!


On Fri, Oct 30, 2020 at 9:20 AM Robert Metzger <rm...@apache.org> wrote:

> It seems that we have consensus to delay the feature freeze.
> I propose to set the *feature freeze to the end of day (CEST) Sunday, Nov
> 8. *
> I'll update the wiki accordingly.
>
> On Fri, Oct 30, 2020 at 4:08 AM Yu Li <ca...@gmail.com> wrote:
>
> > +1 for extending the feature freeze, it would be helpful for more
> thorough
> > testing of the frocksdb upgrade work.
> >
> > Thanks for the consideration and starting the discussion Stephan!
> >
> > Best Regards,
> > Yu
> >
> >
> > On Thu, 29 Oct 2020 at 16:21, Xintong Song <to...@gmail.com>
> wrote:
> >
> > > +1 for one week extension.
> > >
> > > The native Kubernetes HA could also benefit from it.
> > >
> > > Thank you~
> > >
> > > Xintong Song
> > >
> > >
> > >
> > > On Thu, Oct 29, 2020 at 3:59 PM Till Rohrmann <tr...@apache.org>
> > > wrote:
> > >
> > > > Thanks for starting this discussion Stephan. Some of the features I
> > help
> > > > with could also benefit from an extension. Hence, +1 for moving the
> > > feature
> > > > freeze to the 8th of November.
> > > >
> > > > Cheers,
> > > > Till
> > > >
> > > > On Thu, Oct 29, 2020 at 7:16 AM Robert Metzger <rm...@apache.org>
> > > > wrote:
> > > >
> > > > > I have no objections against an extension, if it helps delivering
> > more,
> > > > and
> > > > > stable features in the release.
> > > > >
> > > > > My proposal would hence be to set the 1.12 cutoff date to the
> weekend
> > > of
> > > > > > the 7th/8th and fork the release-1.12 branch on Monday Nov. 9th.
> > > > >
> > > > >
> > > > > Side comment: In the last feature freeze discussion, there were no
> > > > > objections against my proposal to delay the branch forking until
> > master
> > > > is
> > > > > stable. This probably means that we'll have a phase of a week or
> two
> > > > after
> > > > > the feature freeze where no new features are allowed to be merged,
> > and
> > > we
> > > > > solely focus on fixing bugs. The purpose is to avoid the tedious
> > > merging
> > > > of
> > > > > fixes to two branches.
> > > > >
> > > > >
> > > > >
> > > > > On Thu, Oct 29, 2020 at 7:02 AM Zhijiang <
> wangzhijiang999@aliyun.com
> > > > > .invalid>
> > > > > wrote:
> > > > >
> > > > > > Thanks for the consideration, stephan!
> > > > > >
> > > > > > +1 for one week extension of feature freeze, it would be really
> > > helpful
> > > > > > for ongoing batch shuffle improvement.
> > > > > >
> > > > > > Best,
> > > > > > Zhijiang
> > > > > >
> ------------------------------------------------------------------
> > > > > > From:Yuan Mei <yu...@gmail.com>
> > > > > > Send Time:2020年10月29日(星期四) 11:03
> > > > > > To:dev <de...@flink.apache.org>
> > > > > > Subject:Re: [DISCUSS] 1.12 feature freeze date += one week ?
> > > > > >
> > > > > > Hey Stephan,
> > > > > >
> > > > > > Thanks for bringing this up!
> > > > > >
> > > > > > +1 to one week extension for 1.12 feature freeze.
> > > > > >
> > > > > > Things I am working on are under review and one week would
> > definitely
> > > > > ease
> > > > > > my (and reviewers') life a lot.
> > > > > >
> > > > > > Best,
> > > > > >
> > > > > > Yuan
> > > > > >
> > > > > > On Thu, Oct 29, 2020 at 2:13 AM Stephan Ewen <se...@apache.org>
> > > wrote:
> > > > > >
> > > > > > > Hi all!
> > > > > > >
> > > > > > > We are approaching the feature freeze date for the 1.12 release
> > > that
> > > > > was
> > > > > > > discussed earlier.
> > > > > > >
> > > > > > > From my side and the developments I am involved with, we are
> > close
> > > > and
> > > > > in
> > > > > > > good shape, but could really use one more week to round things
> > off.
> > > > It
> > > > > > > would help both the code quality and our mental health a lot
> :-)
> > > > > > >
> > > > > > > From some personal conversations I heard at least from some
> other
> > > > > > > committers a similar sentiment.
> > > > > > >
> > > > > > > My proposal would hence be to set the 1.12 cutoff date to the
> > > weekend
> > > > > of
> > > > > > > the 7th/8th and fork the release-1.12 branch on Monday Nov.
> 9th.
> > > > > > >
> > > > > > > What do you think?
> > > > > > >
> > > > > > > Best,
> > > > > > > Stephan
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSS] 1.12 feature freeze date += one week ?

[Robert Metzger <rm...@apache.org>]

It seems that we have consensus to delay the feature freeze.
I propose to set the *feature freeze to the end of day (CEST) Sunday, Nov
8. *
I'll update the wiki accordingly.

On Fri, Oct 30, 2020 at 4:08 AM Yu Li <ca...@gmail.com> wrote:

> +1 for extending the feature freeze, it would be helpful for more thorough
> testing of the frocksdb upgrade work.
>
> Thanks for the consideration and starting the discussion Stephan!
>
> Best Regards,
> Yu
>
>
> On Thu, 29 Oct 2020 at 16:21, Xintong Song <to...@gmail.com> wrote:
>
> > +1 for one week extension.
> >
> > The native Kubernetes HA could also benefit from it.
> >
> > Thank you~
> >
> > Xintong Song
> >
> >
> >
> > On Thu, Oct 29, 2020 at 3:59 PM Till Rohrmann <tr...@apache.org>
> > wrote:
> >
> > > Thanks for starting this discussion Stephan. Some of the features I
> help
> > > with could also benefit from an extension. Hence, +1 for moving the
> > feature
> > > freeze to the 8th of November.
> > >
> > > Cheers,
> > > Till
> > >
> > > On Thu, Oct 29, 2020 at 7:16 AM Robert Metzger <rm...@apache.org>
> > > wrote:
> > >
> > > > I have no objections against an extension, if it helps delivering
> more,
> > > and
> > > > stable features in the release.
> > > >
> > > > My proposal would hence be to set the 1.12 cutoff date to the weekend
> > of
> > > > > the 7th/8th and fork the release-1.12 branch on Monday Nov. 9th.
> > > >
> > > >
> > > > Side comment: In the last feature freeze discussion, there were no
> > > > objections against my proposal to delay the branch forking until
> master
> > > is
> > > > stable. This probably means that we'll have a phase of a week or two
> > > after
> > > > the feature freeze where no new features are allowed to be merged,
> and
> > we
> > > > solely focus on fixing bugs. The purpose is to avoid the tedious
> > merging
> > > of
> > > > fixes to two branches.
> > > >
> > > >
> > > >
> > > > On Thu, Oct 29, 2020 at 7:02 AM Zhijiang <wangzhijiang999@aliyun.com
> > > > .invalid>
> > > > wrote:
> > > >
> > > > > Thanks for the consideration, stephan!
> > > > >
> > > > > +1 for one week extension of feature freeze, it would be really
> > helpful
> > > > > for ongoing batch shuffle improvement.
> > > > >
> > > > > Best,
> > > > > Zhijiang
> > > > > ------------------------------------------------------------------
> > > > > From:Yuan Mei <yu...@gmail.com>
> > > > > Send Time:2020年10月29日(星期四) 11:03
> > > > > To:dev <de...@flink.apache.org>
> > > > > Subject:Re: [DISCUSS] 1.12 feature freeze date += one week ?
> > > > >
> > > > > Hey Stephan,
> > > > >
> > > > > Thanks for bringing this up!
> > > > >
> > > > > +1 to one week extension for 1.12 feature freeze.
> > > > >
> > > > > Things I am working on are under review and one week would
> definitely
> > > > ease
> > > > > my (and reviewers') life a lot.
> > > > >
> > > > > Best,
> > > > >
> > > > > Yuan
> > > > >
> > > > > On Thu, Oct 29, 2020 at 2:13 AM Stephan Ewen <se...@apache.org>
> > wrote:
> > > > >
> > > > > > Hi all!
> > > > > >
> > > > > > We are approaching the feature freeze date for the 1.12 release
> > that
> > > > was
> > > > > > discussed earlier.
> > > > > >
> > > > > > From my side and the developments I am involved with, we are
> close
> > > and
> > > > in
> > > > > > good shape, but could really use one more week to round things
> off.
> > > It
> > > > > > would help both the code quality and our mental health a lot :-)
> > > > > >
> > > > > > From some personal conversations I heard at least from some other
> > > > > > committers a similar sentiment.
> > > > > >
> > > > > > My proposal would hence be to set the 1.12 cutoff date to the
> > weekend
> > > > of
> > > > > > the 7th/8th and fork the release-1.12 branch on Monday Nov. 9th.
> > > > > >
> > > > > > What do you think?
> > > > > >
> > > > > > Best,
> > > > > > Stephan
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSS] 1.12 feature freeze date += one week ?

[Yu Li <ca...@gmail.com>]

+1 for extending the feature freeze, it would be helpful for more thorough
testing of the frocksdb upgrade work.

Thanks for the consideration and starting the discussion Stephan!

Best Regards,
Yu


On Thu, 29 Oct 2020 at 16:21, Xintong Song <to...@gmail.com> wrote:

> +1 for one week extension.
>
> The native Kubernetes HA could also benefit from it.
>
> Thank you~
>
> Xintong Song
>
>
>
> On Thu, Oct 29, 2020 at 3:59 PM Till Rohrmann <tr...@apache.org>
> wrote:
>
> > Thanks for starting this discussion Stephan. Some of the features I help
> > with could also benefit from an extension. Hence, +1 for moving the
> feature
> > freeze to the 8th of November.
> >
> > Cheers,
> > Till
> >
> > On Thu, Oct 29, 2020 at 7:16 AM Robert Metzger <rm...@apache.org>
> > wrote:
> >
> > > I have no objections against an extension, if it helps delivering more,
> > and
> > > stable features in the release.
> > >
> > > My proposal would hence be to set the 1.12 cutoff date to the weekend
> of
> > > > the 7th/8th and fork the release-1.12 branch on Monday Nov. 9th.
> > >
> > >
> > > Side comment: In the last feature freeze discussion, there were no
> > > objections against my proposal to delay the branch forking until master
> > is
> > > stable. This probably means that we'll have a phase of a week or two
> > after
> > > the feature freeze where no new features are allowed to be merged, and
> we
> > > solely focus on fixing bugs. The purpose is to avoid the tedious
> merging
> > of
> > > fixes to two branches.
> > >
> > >
> > >
> > > On Thu, Oct 29, 2020 at 7:02 AM Zhijiang <wangzhijiang999@aliyun.com
> > > .invalid>
> > > wrote:
> > >
> > > > Thanks for the consideration, stephan!
> > > >
> > > > +1 for one week extension of feature freeze, it would be really
> helpful
> > > > for ongoing batch shuffle improvement.
> > > >
> > > > Best,
> > > > Zhijiang
> > > > ------------------------------------------------------------------
> > > > From:Yuan Mei <yu...@gmail.com>
> > > > Send Time:2020年10月29日(星期四) 11:03
> > > > To:dev <de...@flink.apache.org>
> > > > Subject:Re: [DISCUSS] 1.12 feature freeze date += one week ?
> > > >
> > > > Hey Stephan,
> > > >
> > > > Thanks for bringing this up!
> > > >
> > > > +1 to one week extension for 1.12 feature freeze.
> > > >
> > > > Things I am working on are under review and one week would definitely
> > > ease
> > > > my (and reviewers') life a lot.
> > > >
> > > > Best,
> > > >
> > > > Yuan
> > > >
> > > > On Thu, Oct 29, 2020 at 2:13 AM Stephan Ewen <se...@apache.org>
> wrote:
> > > >
> > > > > Hi all!
> > > > >
> > > > > We are approaching the feature freeze date for the 1.12 release
> that
> > > was
> > > > > discussed earlier.
> > > > >
> > > > > From my side and the developments I am involved with, we are close
> > and
> > > in
> > > > > good shape, but could really use one more week to round things off.
> > It
> > > > > would help both the code quality and our mental health a lot :-)
> > > > >
> > > > > From some personal conversations I heard at least from some other
> > > > > committers a similar sentiment.
> > > > >
> > > > > My proposal would hence be to set the 1.12 cutoff date to the
> weekend
> > > of
> > > > > the 7th/8th and fork the release-1.12 branch on Monday Nov. 9th.
> > > > >
> > > > > What do you think?
> > > > >
> > > > > Best,
> > > > > Stephan
> > > > >
> > > >
> > > >
> > >
> >
>

Re: [DISCUSS] 1.12 feature freeze date += one week ?

[Xintong Song <to...@gmail.com>]

+1 for one week extension.

The native Kubernetes HA could also benefit from it.

Thank you~

Xintong Song



On Thu, Oct 29, 2020 at 3:59 PM Till Rohrmann <tr...@apache.org> wrote:

> Thanks for starting this discussion Stephan. Some of the features I help
> with could also benefit from an extension. Hence, +1 for moving the feature
> freeze to the 8th of November.
>
> Cheers,
> Till
>
> On Thu, Oct 29, 2020 at 7:16 AM Robert Metzger <rm...@apache.org>
> wrote:
>
> > I have no objections against an extension, if it helps delivering more,
> and
> > stable features in the release.
> >
> > My proposal would hence be to set the 1.12 cutoff date to the weekend of
> > > the 7th/8th and fork the release-1.12 branch on Monday Nov. 9th.
> >
> >
> > Side comment: In the last feature freeze discussion, there were no
> > objections against my proposal to delay the branch forking until master
> is
> > stable. This probably means that we'll have a phase of a week or two
> after
> > the feature freeze where no new features are allowed to be merged, and we
> > solely focus on fixing bugs. The purpose is to avoid the tedious merging
> of
> > fixes to two branches.
> >
> >
> >
> > On Thu, Oct 29, 2020 at 7:02 AM Zhijiang <wangzhijiang999@aliyun.com
> > .invalid>
> > wrote:
> >
> > > Thanks for the consideration, stephan!
> > >
> > > +1 for one week extension of feature freeze, it would be really helpful
> > > for ongoing batch shuffle improvement.
> > >
> > > Best,
> > > Zhijiang
> > > ------------------------------------------------------------------
> > > From:Yuan Mei <yu...@gmail.com>
> > > Send Time:2020年10月29日(星期四) 11:03
> > > To:dev <de...@flink.apache.org>
> > > Subject:Re: [DISCUSS] 1.12 feature freeze date += one week ?
> > >
> > > Hey Stephan,
> > >
> > > Thanks for bringing this up!
> > >
> > > +1 to one week extension for 1.12 feature freeze.
> > >
> > > Things I am working on are under review and one week would definitely
> > ease
> > > my (and reviewers') life a lot.
> > >
> > > Best,
> > >
> > > Yuan
> > >
> > > On Thu, Oct 29, 2020 at 2:13 AM Stephan Ewen <se...@apache.org> wrote:
> > >
> > > > Hi all!
> > > >
> > > > We are approaching the feature freeze date for the 1.12 release that
> > was
> > > > discussed earlier.
> > > >
> > > > From my side and the developments I am involved with, we are close
> and
> > in
> > > > good shape, but could really use one more week to round things off.
> It
> > > > would help both the code quality and our mental health a lot :-)
> > > >
> > > > From some personal conversations I heard at least from some other
> > > > committers a similar sentiment.
> > > >
> > > > My proposal would hence be to set the 1.12 cutoff date to the weekend
> > of
> > > > the 7th/8th and fork the release-1.12 branch on Monday Nov. 9th.
> > > >
> > > > What do you think?
> > > >
> > > > Best,
> > > > Stephan
> > > >
> > >
> > >
> >
>

Re: [DISCUSS] 1.12 feature freeze date += one week ?

[Till Rohrmann <tr...@apache.org>]

Thanks for starting this discussion Stephan. Some of the features I help
with could also benefit from an extension. Hence, +1 for moving the feature
freeze to the 8th of November.

Cheers,
Till

On Thu, Oct 29, 2020 at 7:16 AM Robert Metzger <rm...@apache.org> wrote:

> I have no objections against an extension, if it helps delivering more, and
> stable features in the release.
>
> My proposal would hence be to set the 1.12 cutoff date to the weekend of
> > the 7th/8th and fork the release-1.12 branch on Monday Nov. 9th.
>
>
> Side comment: In the last feature freeze discussion, there were no
> objections against my proposal to delay the branch forking until master is
> stable. This probably means that we'll have a phase of a week or two after
> the feature freeze where no new features are allowed to be merged, and we
> solely focus on fixing bugs. The purpose is to avoid the tedious merging of
> fixes to two branches.
>
>
>
> On Thu, Oct 29, 2020 at 7:02 AM Zhijiang <wangzhijiang999@aliyun.com
> .invalid>
> wrote:
>
> > Thanks for the consideration, stephan!
> >
> > +1 for one week extension of feature freeze, it would be really helpful
> > for ongoing batch shuffle improvement.
> >
> > Best,
> > Zhijiang
> > ------------------------------------------------------------------
> > From:Yuan Mei <yu...@gmail.com>
> > Send Time:2020年10月29日(星期四) 11:03
> > To:dev <de...@flink.apache.org>
> > Subject:Re: [DISCUSS] 1.12 feature freeze date += one week ?
> >
> > Hey Stephan,
> >
> > Thanks for bringing this up!
> >
> > +1 to one week extension for 1.12 feature freeze.
> >
> > Things I am working on are under review and one week would definitely
> ease
> > my (and reviewers') life a lot.
> >
> > Best,
> >
> > Yuan
> >
> > On Thu, Oct 29, 2020 at 2:13 AM Stephan Ewen <se...@apache.org> wrote:
> >
> > > Hi all!
> > >
> > > We are approaching the feature freeze date for the 1.12 release that
> was
> > > discussed earlier.
> > >
> > > From my side and the developments I am involved with, we are close and
> in
> > > good shape, but could really use one more week to round things off. It
> > > would help both the code quality and our mental health a lot :-)
> > >
> > > From some personal conversations I heard at least from some other
> > > committers a similar sentiment.
> > >
> > > My proposal would hence be to set the 1.12 cutoff date to the weekend
> of
> > > the 7th/8th and fork the release-1.12 branch on Monday Nov. 9th.
> > >
> > > What do you think?
> > >
> > > Best,
> > > Stephan
> > >
> >
> >
>

Re: [DISCUSS] 1.12 feature freeze date += one week ?

[Robert Metzger <rm...@apache.org>]

I have no objections against an extension, if it helps delivering more, and
stable features in the release.

My proposal would hence be to set the 1.12 cutoff date to the weekend of
> the 7th/8th and fork the release-1.12 branch on Monday Nov. 9th.


Side comment: In the last feature freeze discussion, there were no
objections against my proposal to delay the branch forking until master is
stable. This probably means that we'll have a phase of a week or two after
the feature freeze where no new features are allowed to be merged, and we
solely focus on fixing bugs. The purpose is to avoid the tedious merging of
fixes to two branches.



On Thu, Oct 29, 2020 at 7:02 AM Zhijiang <wa...@aliyun.com.invalid>
wrote:

> Thanks for the consideration, stephan!
>
> +1 for one week extension of feature freeze, it would be really helpful
> for ongoing batch shuffle improvement.
>
> Best,
> Zhijiang
> ------------------------------------------------------------------
> From:Yuan Mei <yu...@gmail.com>
> Send Time:2020年10月29日(星期四) 11:03
> To:dev <de...@flink.apache.org>
> Subject:Re: [DISCUSS] 1.12 feature freeze date += one week ?
>
> Hey Stephan,
>
> Thanks for bringing this up!
>
> +1 to one week extension for 1.12 feature freeze.
>
> Things I am working on are under review and one week would definitely ease
> my (and reviewers') life a lot.
>
> Best,
>
> Yuan
>
> On Thu, Oct 29, 2020 at 2:13 AM Stephan Ewen <se...@apache.org> wrote:
>
> > Hi all!
> >
> > We are approaching the feature freeze date for the 1.12 release that was
> > discussed earlier.
> >
> > From my side and the developments I am involved with, we are close and in
> > good shape, but could really use one more week to round things off. It
> > would help both the code quality and our mental health a lot :-)
> >
> > From some personal conversations I heard at least from some other
> > committers a similar sentiment.
> >
> > My proposal would hence be to set the 1.12 cutoff date to the weekend of
> > the 7th/8th and fork the release-1.12 branch on Monday Nov. 9th.
> >
> > What do you think?
> >
> > Best,
> > Stephan
> >
>
>

Re: [DISCUSS] 1.12 feature freeze date += one week ?

[Zhijiang <wa...@aliyun.com.INVALID>]

Thanks for the consideration, stephan!

+1 for one week extension of feature freeze, it would be really helpful for ongoing batch shuffle improvement.

Best,
Zhijiang
------------------------------------------------------------------
From:Yuan Mei <yu...@gmail.com>
Send Time:2020年10月29日(星期四) 11:03
To:dev <de...@flink.apache.org>
Subject:Re: [DISCUSS] 1.12 feature freeze date += one week ?

Hey Stephan,

Thanks for bringing this up!

+1 to one week extension for 1.12 feature freeze.

Things I am working on are under review and one week would definitely ease
my (and reviewers') life a lot.

Best,

Yuan

On Thu, Oct 29, 2020 at 2:13 AM Stephan Ewen <se...@apache.org> wrote:

> Hi all!
>
> We are approaching the feature freeze date for the 1.12 release that was
> discussed earlier.
>
> From my side and the developments I am involved with, we are close and in
> good shape, but could really use one more week to round things off. It
> would help both the code quality and our mental health a lot :-)
>
> From some personal conversations I heard at least from some other
> committers a similar sentiment.
>
> My proposal would hence be to set the 1.12 cutoff date to the weekend of
> the 7th/8th and fork the release-1.12 branch on Monday Nov. 9th.
>
> What do you think?
>
> Best,
> Stephan
>

Re: [DISCUSS] 1.12 feature freeze date += one week ?

[Yuan Mei <yu...@gmail.com>]

Hey Stephan,

Thanks for bringing this up!

+1 to one week extension for 1.12 feature freeze.

Things I am working on are under review and one week would definitely ease
my (and reviewers') life a lot.

Best,

Yuan

On Thu, Oct 29, 2020 at 2:13 AM Stephan Ewen <se...@apache.org> wrote:

> Hi all!
>
> We are approaching the feature freeze date for the 1.12 release that was
> discussed earlier.
>
> From my side and the developments I am involved with, we are close and in
> good shape, but could really use one more week to round things off. It
> would help both the code quality and our mental health a lot :-)
>
> From some personal conversations I heard at least from some other
> committers a similar sentiment.
>
> My proposal would hence be to set the 1.12 cutoff date to the weekend of
> the 7th/8th and fork the release-1.12 branch on Monday Nov. 9th.
>
> What do you think?
>
> Best,
> Stephan
>