Feature Freeze and Release Testing for 1.14

[Xintong Song <xt...@apache.org>]

Hi devs,

We are approaching the feature freeze of release 1.14. There are a few
things that we'd like to bring to your attention.

*1. Feature Freeze Time*

As we agreed, the feature freeze will happen on *August 16, Monday (end of
day CEST)*.

Here we quote Robert & Dian [1] for what a Feature Freeze means:

*B) What does feature freeze mean?*

After the feature freeze, no new features are allowed to be merged to
> master. Only bug fixes and documentation improvements. The release managers
> will revert new feature commits after the feature freeze.

Rational: The goal of the feature freeze phase is to improve the system
> stability by addressing known bugs. New features tend to introduce new
> instabilities, which would prolong the release process. If you need to
> merge a new feature after the freeze, please open a discussion on the dev@
> list. If there are no objections by a PMC member within 48 (workday) hours,
> the feature can be merged.


*2. Get prepared for the release testing*

During the release testing phase, we will have 1 or 2 syncs per week. The
first release testing sync will be on *August 17, 9am CEST*. Similarly to
the previous bi-weekly syncs, everyone is welcomed to join the meeting
(link can be found on the release wiki page [2]).

In preparation for the release testing, we'd like to ask all contributors
who have contributed major features to this release to do the following.
- Open JIRA tickets for creating *documentation* for new features. Tickets
should be opened with Priority Blocker and FixVersion 1.14.0.
- Open JIRA tickets for *testing* new features. Tickets should be opened
with Priority Blocker, FixVersion 1.14.0 and Label release-testing.
- For features listed in the release wiki page [2], please also update the
page with related documentation and testing tickets. If a feature does not
need documentation / testing tasks, please comment explicitly.

Thank you~
Joe, Dawid & Xintong

[1]
https://lists.apache.org/thread.html/ra0ae9d8fb6ae1a3c031dc50368eaf000a023b8c78e48797611a882e8%40%3Cdev.flink.apache.org%3E
[2] https://cwiki.apache.org/confluence/display/FLINK/1.14+Release

Re: Feature Freeze and Release Testing for 1.14

[Yangze Guo <ka...@gmail.com>]

Thanks for the information, Joe, Dawid and Xintong!

I've created the ticket for testing the fine-grained resource
management and updated the wiki page.

Best,
Yangze Guo

On Thu, Aug 12, 2021 at 4:59 PM Xintong Song <xt...@apache.org> wrote:
>
> Hi devs,
>
> We are approaching the feature freeze of release 1.14. There are a few
> things that we'd like to bring to your attention.
>
> *1. Feature Freeze Time*
>
> As we agreed, the feature freeze will happen on *August 16, Monday (end of
> day CEST)*.
>
> Here we quote Robert & Dian [1] for what a Feature Freeze means:
>
> *B) What does feature freeze mean?*
>
> After the feature freeze, no new features are allowed to be merged to
> > master. Only bug fixes and documentation improvements. The release managers
> > will revert new feature commits after the feature freeze.
>
> Rational: The goal of the feature freeze phase is to improve the system
> > stability by addressing known bugs. New features tend to introduce new
> > instabilities, which would prolong the release process. If you need to
> > merge a new feature after the freeze, please open a discussion on the dev@
> > list. If there are no objections by a PMC member within 48 (workday) hours,
> > the feature can be merged.
>
>
> *2. Get prepared for the release testing*
>
> During the release testing phase, we will have 1 or 2 syncs per week. The
> first release testing sync will be on *August 17, 9am CEST*. Similarly to
> the previous bi-weekly syncs, everyone is welcomed to join the meeting
> (link can be found on the release wiki page [2]).
>
> In preparation for the release testing, we'd like to ask all contributors
> who have contributed major features to this release to do the following.
> - Open JIRA tickets for creating *documentation* for new features. Tickets
> should be opened with Priority Blocker and FixVersion 1.14.0.
> - Open JIRA tickets for *testing* new features. Tickets should be opened
> with Priority Blocker, FixVersion 1.14.0 and Label release-testing.
> - For features listed in the release wiki page [2], please also update the
> page with related documentation and testing tickets. If a feature does not
> need documentation / testing tasks, please comment explicitly.
>
> Thank you~
> Joe, Dawid & Xintong
>
> [1]
> https://lists.apache.org/thread.html/ra0ae9d8fb6ae1a3c031dc50368eaf000a023b8c78e48797611a882e8%40%3Cdev.flink.apache.org%3E
> [2] https://cwiki.apache.org/confluence/display/FLINK/1.14+Release