Re: [PR] Add Flink 1.19.2 release [flink-web]

2025-02-19 Thread via GitHub
afedulov merged PR #771: URL: https://github.com/apache/flink-web/pull/771 -- 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.apac

Re: [PR] Add Flink 1.19.2 release [flink-web]

2025-02-12 Thread via GitHub
afedulov commented on code in PR #771: URL: https://github.com/apache/flink-web/pull/771#discussion_r1952719865 ## 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" +

Re: [PR] Add Flink 1.19.2 release [flink-web]

2025-02-12 Thread via GitHub
ferenc-csaky commented on code in PR #771: URL: https://github.com/apache/flink-web/pull/771#discussion_r195992 ## 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.000

Re: [PR] Add Flink 1.19.2 release [flink-web]

2025-02-11 Thread via GitHub
leonardBang commented on code in PR #771: URL: https://github.com/apache/flink-web/pull/771#discussion_r1951908382 ## 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

Re: [PR] Add Flink 1.19.2 release [flink-web]

2025-02-11 Thread via GitHub
ferenc-csaky commented on code in PR #771: URL: https://github.com/apache/flink-web/pull/771#discussion_r195992 ## 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.000

Re: [PR] Add Flink 1.19.2 release [flink-web]

2025-01-29 Thread via GitHub
afedulov commented on PR #771: URL: https://github.com/apache/flink-web/pull/771#issuecomment-2621398571 TODO: add Netty 4 disclaimer. -- 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