Hi Xingbo, I just notice that 1.16.0 didn't release yet after I merge https://github.com/apache/flink/pull/20798 into the release branch. Sorry for making this change.
This is a trivial change but if you'd like to revert it, please do it and comment in the original PR. Best, tison. Xingbo Huang <hxbks...@gmail.com> 于2022年9月6日周二 16:09写道： > I would like to give you a brief update of the Flink 1.16 release sync > meating of 2022-09-06. > > *We have cut release-1.16 branch yesterday(5th of September 2022). It is > expected that we will prepare rc0 for further testing in a few days* > > *We're almost done with x-team testing[1]. The remaining test issues are > also expected to be finished in the next two days.* > > *Currently, there are 4 blocker issues which are being worked on. Many > thanks to these contributors and reviewers. > - FLINK-29120 <https://issues.apache.org/jira/browse/FLINK-29120>, > FLINK-28975 <https://issues.apache.org/jira/browse/FLINK-28975>, > FLINK-28941 > <https://issues.apache.org/jira/browse/FLINK-28941>, FLINK-29196 > <https://issues.apache.org/jira/browse/FLINK-29196> > > *We have finished the license check and only found a license problem* > > *We still have some critical test stabilities[2] need to be resolved* > > For more information about Flink release 1.16, you can refer to > https://cwiki.apache.org/confluence/display/FLINK/1.16+Release > > The next Flink release sync will be on Tuesday the 13th of September at 9am > CEST/ 3pm China Standard Time / 7am UTC. The link could be found on the > following page > > https://cwiki.apache.org/confluence/display/FLINK/1.16+Release#id-1.16Release-Syncmeeting > . > > On behalf of all the release managers, > > best regards, > Xingbo > > [1] https://issues.apache.org/jira/browse/FLINK-28896 > [2] > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20priority%20in%20(Blocker%2C%20Critical)%20AND%20fixVersion%20%3D%201.16.0%20ORDER%20BY%20summary%20ASC%2C%20priority%20DESC >
