snuyanzin commented on code in PR #825: URL: https://github.com/apache/flink-web/pull/825#discussion_r2764176103
########## 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: I'm ok about monthly basis my point is that if we reference at least one thing and telling about recent years, like in this sentence >In the last few years the Flink PR backlog got to around 1200. We introduced the stale bot last year, and it came down to around 200. then other features/events should be also considered in same time range -- 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]
