Dear Fluss PPMC and mentors, Here's the draft for this quarter's podling report. Looking forward to any feedback and please sign-off when you are able.
I also updated it at the cwiki: https://cwiki.apache.org/confluence/spaces/INCUBATOR/pages/435028221/July2026#fluss Best, Jark Wu ------------------------------------------------------------------------------------------------------------ ## Fluss Fluss is a streaming storage built for real-time analytics which can serve as the real-time data layer for Lakehouse architectures. Fluss has been incubating since 2025-06-04. ### Three most important unfinished issues to address before graduating: None. The community has completed the maturity model and started the graduation process on general@incubator. The graduation vote is currently underway. ### Are there any issues that the IPMC or ASF Board need to be aware of? None at this time. ### How has the community developed since the last report? 1. Elected 1 new committer: Anton Borisov. 2. Held regular [Monthly Community Calls](https://s.apache.org/fluss-community-call) in April, May. (June was postponed to 3rd July) 3. Community presentations and outreach continued: - [Flink Forward Asia 2026](https://asia.flink-forward.org/) was held on June 26-27 in Shenzhen, China, with many Fluss-related talks. - OpenXData 2026 included Fluss talks and panels, including a Fluss presentation by Mehul Batra and a community panel involving Yuxia Luo from the Fluss PPMC. - Anton Borisov presented a Fluss talk at a Data Streaming meetup in London on May 7. ### How has the project developed since the last report? - Released Apache Fluss 0.9.1-incubating on 2026-05-04. Apache Fluss 0.9.1 is currently the latest stable release. - Completed the Apache release of fluss-rust 0.1.0-incubating, the first official Rust, Python, and C++ client release for Apache Fluss. - Continued development toward Apache Fluss 1.0.0, including real-time AI and ML use cases, real-time lakehouse integrations, streaming analytics, cloud-native operations, client SDKs, and security improvements. - Published more technical and user-facing content, including articles on pruning, real-time deduplication, Taobao Instant Commerce, storage hierarchy, and tiering service operations. ### How would you assess the podling's maturity? - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: Commentary: The project has established a regular Apache release cadence, continued to grow its committer base, and is showing healthy technical and community activity. Fluss has shipped multiple Apache Incubator releases, expanded its ecosystem with native multi-language clients, and published more production-oriented technical content. The community has completed the maturity model and started the graduation process. ### Date of last release: 2026-05-04 (Apache Fluss 0.9.1-incubating) ### When were the last committers or PPMC members elected? The most recent committer was Anton Borisov, elected in May. No new PPMC member has been elected since the April report. Two existing committers have been included in the proposed PMC roster for graduation. ### Have your mentors been helpful and responsive? Yes. The mentors have been helpful and responsive. No open issues at this time. ### Is the PPMC managing the podling's brand / trademarks? Yes. The PPMC is actively managing the Apache Fluss (Incubating) brand and trademarks. The PPMC has fixed several branding issues related to external blogs and content, including pages on Alibaba Cloud and Ververica websites. There are no known open brand or trademark issues at this time. ### Signed-off-by: - [ ] (fluss) Jean-Baptiste Onofré Comments: - [ ] (fluss) Becket Qin Comments: - [ ] (fluss) Yu Li Comments: - [ ] (fluss) Jingsong Lee Comments: - [ ] (fluss) Zili Chen Comments: ### IPMC/Shepherd notes: ---------- Forwarded message --------- From: <[email protected]> Date: Thu, 25 Jun 2026 at 18:10 Subject: Podling Fluss Report Reminder - July 2026 To: <[email protected]> Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 15 July 2026. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, July 01). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Candidate names should not be made public before people are actually elected, so please do not include the names of potential committers or PPMC members in your report. Thanks, The Apache Incubator PMC Submitting your Report ---------------------- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://cwiki.apache.org/confluence/display/INCUBATOR/July2026 Note: This is manually populated. You may need to wait a little before this page is created from a template. Note: The format of the report has changed to use markdown. Mentors ------- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
