davidradl commented on code in PR #832: URL: https://github.com/apache/flink-web/pull/832#discussion_r2925841478
########## docs/content/posts/2026-03-01-community-update.md: ########## @@ -0,0 +1,146 @@ +--- +authors: +- davidrad: null + name: David Radley +date: "2026-03-01T08:00:00Z" +excerpt: Flink Community update for March 2026 +title: Flink Community update for March 2026 +aliases: +- /news/2026/03/01/community-update.html +--- + +<!-- TOC --> + * [What happened last month](#what-happened-last-month) + * [Blogs](#blogs) + * [Apache Flink Dev List activity](#apache-flink-dev-list-activity) + * [Key Themes](#key-themes) + * [Community Announcements](#community-announcements) + * [FLIP Activity](#flip-activity) + * [Accepted - being implemented](#accepted---being-implemented) + * [Being discussed](#being-discussed) + * [Kubernetes Operator 1.14.0 Release](#kubernetes-operator-1140-release) + * [Apache Flink Connector Parent 2.0.0 Release](#apache-flink-connector-parent-200-release) + * [Apache Flink Connector AWS 6.0 Release](#apache-flink-connector-aws-60-release) + * [Apache Flink Agents 0.2.0 released](#apache-flink-agents-020-released) + * [For more information](#for-more-information) +<!-- TOC --> + +Previous Blog: [Flink community update February 2026](https://flink.apache.org/2026/02/01/flink-community-update-february26/) + +A strong February; there was a lot of commit activity with 320 open PRs and 4 new releases. Review Comment: @snuyanzin I understand your point. If I had taken a screen shot of the repo pulse then I could have got a view of the core repository, but unfortunately I did not do that and that would be just for one repo. If I write a script to find the the number of opened PRs and merged PRs, I would need to do this for each repo that was active. I can do that, but a lot of the feedback from last month is that this should be evidence based. I could publish the script in the repo and link to it. What do you think of this as a way forward? -- 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]
