Hi,all, I want to merge a pr (https://github.com/apache/flink/pull/18363) belonging to FLIP-190, which was approved yesterday, but not merged before code freeze because of CI queueing and failed by other changes. WDYT?
Best, Wenlong On Thu, 17 Feb 2022 at 02:08, Till Rohrmann <trohrm...@apache.org> wrote: > Hi everyone, > > The deadline for merging new features for Flink 1.15 has passed. > > * From now on, only bug-fixes and documentation fixes / improvements are > allowed to be merged into the master branch. > > * New features merged after this point can be reverted. If you need an > exception to this rule, please open a discussion on dev@ list and reach > out > to us. > > We plan to wait for the master branch to get a bit more stabilized before > cutting the "release-1.15" branch, in order to reduce the overhead of > having to manage two branches. That also means potentially delaying merging > new features for Flink 1.16 into the master branch. If you are blocked on > this, please let us know and we can come up with a compromise for the > branch cutting time. > > What you can do to help with the release testing phase: > > * The first release testing sync will be on *February 22, 9am CET*. > Everyone is welcome to join. The link can be found on the release wiki page > [1]. > > * Please prepare for the release testing by creating Jira tickets for > documentation and testing tasks for the new features. Tickets should be > opened with Priority Blocker, FixVersion 1.15.0 and Label release-testing > (testing tasks only). > > * There are currently 92 test-stability issues affecting the 1.15.0 release > [2]. It is greatly appreciated if you can help address some of them. > > Cheers, > Joe, Yun & Till > > [1] https://cwiki.apache.org/confluence/display/FLINK/1.15+Release > [2] https://issues.apache.org/jira/issues/?filter=12351363 >
