Hi Martjin, I have discussed offline with several contributors from China and found that most of them thought it difficult to finish the on-going features by 25th July. As there is consensus[1][2] that the feature freeze will happen by the end of July with potentially two weeks delay, do you think it makes sense to postpone the feature freeze date a bit(maybe two weeks or so) as there are still 44 planned tasks are on-going and only 8 of them are finished[3]?
Regarding the release branch cut time, in previous releases, after feature freeze, it usually waits about two weeks or so before cutting the release branch. This could avoid pushing to two branches at the same time which may happen more frequently than usual. Should we also follow that practice in this release? Best, Xingbo [1] https://lists.apache.org/thread/ghfb5xdjy7tv0zqlrxvh3hcsc740w4ml [2] https://www.mail-archive.com/dev@flink.apache.org/msg56702.html [3] https://cwiki.apache.org/confluence/display/FLINK/1.16+Release Martijn Visser <martijnvis...@apache.org> 于2022年7月5日周二 17:32写道： > Hi everyone, > > We've just finished our 1.16 release sync update and would like to update > you on the current status and request for your help: > > 1. The Flink 1.16 release branch is expected to be cut in 3 weeks, which > means that we will cut the release branch and start with the release > testing. New features that didn't make that time will be postponed until > the Flink release after this one. > > 2. Please help make it easier for the release managers by making sure that > the Flink 1.16 release page is updated [1]. This means that: > > * There should be a Jira link on the release page > * This is assigned to someone > * The release page has the latest state reflected > * When a Jira ticket is completed, proper release notes have been added to > the Jira ticket. > > 3. There are numerous test instabilities which we need help with to get > fixed. We currently have 1 release blocker and numerous critical test > stability tickets open. You can see an overview of these also on the > release page [2]. Please help the release managers with: > > * Volunteering to pick up a test instability ticket. You can ping me > (martijnvisser) to get it assigned to you. > * Please also mark the ticket as 'In Progress' when you're working on it > and 'Stop Progress' if you're not working on it anymore, so that we know > who is working on which ticket. > > Current open test instability tickets that needs a volunteer to review > and/or create fix are https://issues.apache.org/jira/browse/FLINK-26979 > (reviewer), https://issues.apache.org/jira/browse/FLINK-28398, > https://issues.apache.org/jira/browse/FLINK-28392 and > https://issues.apache.org/jira/browse/FLINK-26402. > > Best regards, > > Martijn > > [1] https://cwiki.apache.org/confluence/display/FLINK/1.16+Release > [2] > > https://cwiki.apache.org/confluence/display/FLINK/1.16+Release#id-1.16Release-2022-07-05 >
