davidradl commented on code in PR #825: URL: https://github.com/apache/flink-web/pull/825#discussion_r2764125751
########## docs/content/posts/2026-02-01-community-update.md: ########## @@ -0,0 +1,108 @@ +--- +authors: +- davidrad: null + name: David Radley +date: "2026-02-02T08:00:00Z" +excerpt: Flink Community update for February 2026 +title: Flink Community Update - February'26 +aliases: +- /news/2026/02/02/community-update.html +--- + +# This past month in Flink + +<!-- TOC --> +* [This past month in Flink](#this-past-month-in-flink) + * [Flink related Blogs](#flink-related-blogs) + * [Summary of Apache Flink Dev List (covering January 2026)](#summary-of-apache-flink-dev-list-covering-january-2026) + * [Key Themes](#key-themes) + * [Community Announcements](#community-announcements) + * [Active FLIPs](#active-flips) + * [Kubernetes Operator 1.14.0 Release](#kubernetes-operator-1140-release) + * [For more information](#for-more-information) +<!-- TOC --> + +Previous Blog : +[https:/flink.apache.org/2020/09/04/flink-community-update-august20/](https:/flink.apache.org/2020/09/04/flink-community-update-august20/) + +After a gap, the Community update is back for February 2026! As usual this update will summarise what has happened in the previous month (January). Review Comment: Hi @snuyanzin, yes i think this is a valid consideration. This blog is intended to review the previous months activity on a monthly basis - I was hoping to keep this scope so we can get it out in a timely manner. I suggest that something like what you are proposing could be produced collaboratively, separately, as a bridging blog. How about I start a discussion on the dev list to solicit content for such a blog? Once I have the material I am happy to author a new blog on this. Then I can edit this blog to reference the new blog. WDYT? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
