ferenc-csaky commented on code in PR #771: URL: https://github.com/apache/flink-web/pull/771#discussion_r1951111992
########## docs/content/posts/2025-02-TBD-release-1.19.2.md: ########## @@ -0,0 +1,212 @@ +--- +title: "Apache Flink 1.19.2 Release Announcement" +date: "2025-02-TBDT00:00:00.000Z" +aliases: +- /news/2025/02/TBD/release-1.19.2.html +authors: +- afedulov: + name: "Alexander Fedulov" + +--- + +The Apache Flink Community is pleased to announce the second bug fix release of the Flink 1.19 series. + +This release includes 73 bug fixes, vulnerability fixes, and minor improvements for Flink 1.19. +Below you will find a list of all bugfixes and improvements (excluding improvements to the build infrastructure and build stability). For a complete list of all changes see: +[JIRA](https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12354783). + +We highly recommend all users upgrade to Flink 1.19.2. + Review Comment: To explicitly notify users about the Netty4 update in flink-rpc, we could add a new section here: ```md # Highligts ## Updated Flink RPC to Netty4 Flink uses [Apache Pekko](https://pekko.apache.org) for RPC communication, that uses Netty. In a recent Pekko version, that logic was updated from Netty3 to Netty4, which made it possible for Flink to drop Netty3 completely. This is important, because Netty3 reached its end of life since years and have quite some open CVEs. The Flink community agreed that it was worth to release this update in a patch version, although there are some minor discrepancies in the default memory allocation between Netty3 and Netty4. By default Netty4 allocates slightly more memory for improved performance. We believe this change will not affect the vast majority of use-cases at all. To understand the differences in detail and the possible configurations, please check the relevant part of the [Flink documentation]({{< param DocsBaseUrl >}}flink-docs-release-1.19/docs/deployment/memory/mem_tuning/#configure-memory-for-netty4). doc ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
