+1 for release flink-1.17.1 The blocker issue might cause silent incorrect data, it's better to have a fix release ASAP.
Best Yun Tang ________________________________ From: weijie guo <guoweijieres...@gmail.com> Sent: Thursday, May 11, 2023 11:08 To: dev@flink.apache.org <dev@flink.apache.org>; tonysong...@gmail.com <tonysong...@gmail.com> Subject: [DISCUSS] Release Flink 1.17.1 Hi all, I would like to discuss creating a new 1.17 patch release (1.17.1). The last 1.17 release is nearly two months old, and since then, 66 tickets have been closed [1], of which 14 are blocker/critical [2]. Some of them are quite important, such as FLINK-31293 [3] and FLINK-32027 [4]. I am not aware of any unresolved blockers and there are no in-progress tickets [5]. Please let me know if there are any issues you'd like to be included in this release but still not merged. If the community agrees to create this new patch release, I could volunteer as the release manager and Xintong can help with actions that require a PMC role. Thanks, Weijie [1] https://issues.apache.org/jira/browse/FLINK-32027?jql=project%20%3D%20FLINK%20AND%20fixVersion%20%3D%201.17.1%20%20and%20resolution%20%20!%3D%20%20Unresolved%20order%20by%20priority%20DESC [2] https://issues.apache.org/jira/browse/FLINK-31273?jql=project%20%3D%20FLINK%20AND%20fixVersion%20%3D%201.17.1%20and%20resolution%20%20!%3D%20Unresolved%20%20and%20priority%20in%20(Blocker%2C%20Critical)%20ORDER%20by%20priority%20%20DESC [3] https://issues.apache.org/jira/browse/FLINK-31293 [4] https://issues.apache.org/jira/browse/FLINK-32027 [5] https://issues.apache.org/jira/projects/FLINK/versions/12352886
