FINAL REPORT - DO NOT EDIT

NOTE that the content for this month report is in markdown format- please do not remove any formatting characters when adding your reports.

If your report is missing please use the clutch2report.py script to generate your report.

It also best to:

Do not change existing formatting. Especially do not change the formatting of the sign-off area.
Keep all lines under 76 characters long.
All content under the ### headings should be indented by two spaces. Do not use tabs.
Please don't change the text in the headings or add new ones.
Include one space after a bullet point or full stop on a numbered list.
Use [X] (X and no spaces) to sign off reports.
Do not include long URLs and use the apache URL shortener https://s.apache.org.
Please note that some lines have two spaces at the end. Do not remove these spaces.

Please make sure you use the current report and don't copy an old one, the headings do change from time to time.

A script will be run on this report before it is submitted to the board. If your lines are too long it may insert line breaks in unexpected places.

Reflow

fold -w 76 -s $1 | cat -s

Timeline

Wed April 01	Podling reports due by end of day
Sun April 05	Shepherd reviews due by end of day
Sun April 05	Summary due by end of day
Tue April 07	Mentor signoff due by end of day
Wed April 08	Report submitted to Board
Wed April 15	Board meeting

Shepherd Assignments

Calvin Kirs	Fluss
Dave Fisher	Caldera
Drew Farris	Livy
Justin Mclea	Pegasus
P. Taylor Goetz	OzHera
PJ Fanning	Amoro
Timothy Chen	Pony Mail
Willem Jiang	ResilientDB
Xuanwo	HugeGraph

Incubator PMC report for April 2026

The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts.

As of March, there are 28 podlings under incubation and three releases were made. There were no additions or removals to IPMC membership.

Mailing list traffic during the month focused on release voting, graduation discussions, retirement votes, discussion of a possible xdigest proposal, and the Community Over Code Glasgow Incubator track CFP.

Baremaps and HoraeDB have retired as part of normal Incubator lifecycle management.

A discussion on the mailing list raised concerns about Caldera's current status, including low participation and limited ASF engagement.

Several podlings, including Burr, Fluss, and Geaflow, are undergoing their scheduled 6-month reviews.

Livy has started discussions on graduation on its mailing list.

ResilientDB continues to make progress toward graduation, although delays in release voting suggest the podling may need to seek additional mentor engagement.

Pegasus continues to work on community revitalisation.

Fluss is ready to graduate.

Most other podlings continue to make steady progress toward graduation.

Two podlings, Caldera and Pony Mail failed to submit a report and will be asked to report next month. When this was written, Pegasus was missing mentor signoff.

Community

New IPMC members:

Jark Wu

People who left the IPMC:

None

New Podlings

None

Podlings that failed to report, expected next month

Caldera
Pony Mail

Graduations

None

The board has motions for the following:

None

Releases

The following releases entered distribution during the month of March:

Auron 7.0.0
Fluss 0.9.0
Seata-go v2.1.0

IP Clearance

None

Legal / Trademarks

N/A

Infrastructure

N/A

Amoro

Amoro is a Lakehouse management system built on open data lake formats like Apache Iceberg and Apache Paimon.

Amoro has been incubating since 2024-03-11.

Three most important unfinished issues to address before graduating:

Fix possible and potential security vulnerability issues.
Release more versions under ASF.
Initiate the discussion on graduating from the ASF Incubator and complete some preparatory work.

Are there any issues that the IPMC or ASF Board need to be aware of?

Currently no.

How has the community developed since the last report?

Added 4 new contributors

How has the project developed since the last report?

Merged 62 PRs

How would you assess the podling's maturity?

Please feel free to add your own commentary.

Initial setup
Working towards first release
Community building
Nearing graduation
Other:

Date of last release:

2025-09-11, released Amoro 0.8.1-incubatiing

The community is preparing for the 0.9.0-incubating release. As this version will bring significant architectural improvements, the community may need more time to complete its validation.

When were the last committers or PPMC members elected?

2026-01-07, committer:Fei Wang(turboFei)

Have your mentors been helpful and responsive?

Yes, Amoro's mentors actively participate in the project, contribute insights, and help advance the project towards graduation.

Is the PPMC managing the podling's brand / trademarks?

Yes, everything is fine.

Signed-off-by:

(amoro) Justin Mclean
Comments:
(amoro) Zhongyi Tan
Comments:
(amoro) Yu Li
Comments: The addition of a new committer reflects the continued growth of community diversity, as we look forward to the 0.9.0 release and progress toward graduation.
(amoro) Xinyu Zhou
Comments:
(amoro) Kent Yao
Comments:

IPMC/Shepherd notes:

Caldera

Caldera provides a modular platform for modeling, scripting, and executing adversary behavior. It allows users to construct emulation plans, provides agents for communicating with the command and control server, and enables users to evaluate security detections in a structured, scalable, and repeatable way. With the use of plug- ins and community-contributed features, Caldera supports a range of use cases including adversary emulation, purple teaming, detection engineering, and continuous security validation. Using Caldera, defenders can emulate known threat actor behavior and perform other red team activity to evaluate their organization’s defensive capabilities, test analytics, and find detection gaps. As a modular tool based on the MITRE ATT&CK framework, Caldera is designed to be extensible, intelligence-driven, and automation-friendly.

Caldera has been incubating since 2025-12-19.

Three most important unfinished issues to address before graduating:

Are there any issues that the IPMC or ASF Board need to be aware of?

How has the community developed since the last report?

How has the project developed since the last report?

How would you assess the podling's maturity?

Please feel free to add your own commentary.

Initial setup
Working towards first release
Community building
Nearing graduation
Other:

Date of last release:

XXXX-XX-XX

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

Is the PPMC managing the podling's brand / trademarks?

Signed-off-by:

(caldera) Kevin Ratnasekera
Comments:
(caldera) Francis Chuang
Comments:
(caldera) PJ Fanning
Comments: No PPMC member or mentor (except me) has yet signed up to any mailing list. I have been told that Mitre Legal team are ready to sign the SGA but the Caldera team email me and refuse to use the lists, despite me constantly telling them to. It may be time to consider having IPMC retire the podling.
(caldera) Gordon King
Comments:

IPMC/Shepherd notes:

Justin Mclean: See discussion on Incubator general list https://lists.apache.org/thread/hmw6zxzc60pktfjk8p2tmn66pzfmvfpw

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:

Complete more Apache releases: finalizing the Fluss-Rust 0.1.0 RC voting process and planning the Fluss 0.9.1 release for April.
Grow the community and attract more committers, contributors and users.
Fill out the maturity model and graduation preparations

Are there any issues that the IPMC or ASF Board need to be aware of?

There are no critical issues to report at this time. The team is currently preparing for the first release of Fluss-Rust, which includes C++ and Python bindings. We expect to initiate the IPMC voting process within the next few days.

How has the community developed since the last report?

Add 2 new committers (Liebing Yu and Keith Lee), currently with total 19 committers.
Add 1 new PPMC member (Mehul Batra), the first invited PPMC member since incubation, currently with total 14 PPMC members (including mentors).
Held regular monthly community calls in January, February, and March.
Community presentations and outreach:

Fluss PPMC members presented at the joint "Apache Fluss × Apache Iceberg" webinar on January 20, 2026.
Giannis Polyzos spoke at QCon London on March 17, 2026.

How has the project developed since the last report?

Released version 0.9.0 on March 2, 2026, marking the second official release under the Apache Incubator. This milestone reflects three months of collaborative development featuring over 400 commits and 12 highlighted features from the community.
Initiated the release of Fluss-Rust 0.1.0, which includes C++ and Python SDKs. This represents the first multi-language client version for Fluss, comprising over 200 commits from 27 contributors.
Active development is underway for version 1.0.0, with a target release date in June 2026.
The community discussed and finalized the project roadmap for 2026.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

Initial setup
Working towards first release
Community building
Nearing graduation
Other:

Date of last release:

2026-03-02 (v0.9.0)

When were the last committers or PPMC members elected?

2026-03-10

Have your mentors been helpful and responsive?

Yes.

Is the PPMC managing the podling's brand / trademarks?

Yes, everything is fine.

Signed-off-by:

(fluss) Jean-Baptiste Onofré
Comments: I think Fluss is pretty close to graduation. Maybe worth to start evaluating the maturity model and other preparation steps.
(fluss) Becket Qin
Comments: I agree that Fluss is making steady progress and close to graduation.
(fluss) Yu Li
Comments: It's great to see new committers and a PMC member joining, which indicates a more diverse community. Regular sync meetings and consistent releases further reflect robust community development, and I'm confident the project is steadily progressing toward graduation.
(fluss) Jingsong Lee
Comments: +1 to fluss is close to graduation. I have seen a lot of participants working together to make the Fluss community better.
(fluss) Zili Chen
Comments:

IPMC/Shepherd notes:

Livy

Livy is web service that exposes a REST interface for managing long running Apache Spark contexts in your cluster. With Livy, new applications can be built on top of Apache Spark that require fine grained interaction with many Spark contexts.

Livy has been incubating since 2017-06-05.

Three most important unfinished issues to address before graduating:

Revitalization of the Community
Dependable Release Cadence
Keep the project up to date with security fixes and in terms of Spark support

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?

New mailing list activity around project graduation. Automatic closure of inactive PRs was implemented to help clean up abandoned PRs.

How has the project developed since the last report?

A new release is available and some new fixes and improvements are merged for the upcoming release.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

Initial setup
Working towards first release
Community building
Nearing graduation
Other:

Date of last release:

2026-02-11

When were the last committers or PPMC members elected?

October 2023

Have your mentors been helpful and responsive?

Yes

Is the PPMC managing the podling's brand / trademarks?

No answer

Signed-off-by:

(livy) Bikas Saha
Comments:
(livy) Luciano Resende
Comments:
(livy) Jean-Baptiste Onofré
Comments: Clearly Livy is ready to graduate. Discussion started.
(livy) Madhawa Kasun Gunasekara
Comments:
(livy) Larry McCay
Comments:
(livy) Gyorgy Gal
Comments:

IPMC/Shepherd notes:

OzHera

OzHera is an application observation platform (APM) in the era of cloud native, with the application as its core, integrating capabilities such as metric monitoring, trace tracking, logging, and alerting

OzHera has been incubating since 2024-07-11.

Three most important unfinished issues to address before graduating:

Increase Release Cadence: Work towards establishing a regular and predictable Apache release cadence to demonstrate project stability.
Community Diversity: Expand and cultivate a more diverse community of contributors from multiple organizations.
Complete Name Search & Trademark: Conduct the formal Podling Name Search and finalize the transfer of the project name to the ASF.

Are there any issues that the IPMC or ASF Board need to be aware of?

No.

How has the community developed since the last report?

The community has maintained an active pace of development and collaboration, with ongoing discussions and Pull Request reviews across the various modules.
We continue to welcome and onboard new potential contributors by improving documentation and developer guides.

How has the project developed since the last report?

This period has seen significant activity across the project, focusing on enhancing agent capabilities, improving architecture, and expanding platform functionality.

Hera Agent Enhancements: Significant improvements were made to the Hera Agent to improve data collection and performance:
Feature: Added configuration parameter support and a dynamic sending frequency limit to control data flow.
Optimization: Optimized the agent channel map to prioritize IP-based lookups for improved efficiency.
Stability: Implemented verification for agent request body JSON format and optimized log processing and configuration delivery logic.
New Capabilities: Added new interfaces for agent invocation.
Platform & Architectural Optimizations: Key enhancements to the core platform architecture were merged:
Scalability: Initiated "Business Decomposition" to improve the platform's ability to scale with growing needs.
Dynamic Configuration: Integrated Nacos configuration center to support dynamic configuration management across the ecosystem.
Metric & Permission Extensions: Refactored the hera_app_role table primary key to bigint, and extended the Metric class to support server environment IDs.
Logging: Added log query tools and optimizations to improve log collection logic.
Observability Capabilities: Expanded platform-level visibility and alerting:
Alerting: Added new alarm strategy types and optimized parameter filling flow for alarm rules.
Permission Management: Enhanced member limit controls for application permissions.
Critical Bug Fixes: Several important fixes were merged:
Corrected the spelling for promql.
Fixed Redis import path errors and pipeline execution logic issues.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

Initial setup
Working towards first release
Community building
Nearing graduation
Other:

Date of last release:

2025-03-26

When were the last committers or PPMC members elected?

2025-01-13

Have your mentors been helpful and responsive?

Yes.

Is the PPMC managing the podling's brand / trademarks?

The PPMC is aware of and in the process of initiating the brand and trademark management tasks, including the necessary Podling Name Search.

Signed-off-by:

(ozhera) Yu Xiao
Comments:
(ozhera) Yu Li
Comments: It's great to see a new release delivered. Look forward to continued growth in community diversity.
(ozhera) Kevin Ratnasekera
Comments:
(ozhera) Duo Zhang
Comments:

IPMC/Shepherd notes:

Pegasus

Pegasus is a distributed key-value storage system which is designed to be simple, horizontally scalable, strongly consistent and high-performance.

Pegasus has been incubating since 2020-06-28.

Three most important unfinished issues to address before graduating:

We are working to revitalize the community, including cultivating more active contributors and promoting regular releases.

Are there any issues that the IPMC or ASF Board need to be aware of?

A contributor has proposed a plan for the 2.5.1 release on the mailing list, outlining potential features and bug fixes to be included. PPMC members and committers have responded, and the community is actively moving forward in this direction.

How has the community developed since the last report?

Recently, a total of 7 contributors (including committers) have been submitting code toward the upcoming 2.6.0 release as well as the near-term 2.5.1 release.

How has the project developed since the last report?

The community is actively working toward the 2.5.1 release, and code reviews are being carried out for the submitted pull request.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

Initial setup
Working towards first release
Community building
Nearing graduation
Other:

Date of last release:

2023-12-12

When were the last committers or PPMC members elected?

2024-09-26

Have your mentors been helpful and responsive?

No issues were encountered that required mentor assistance.

Is the PPMC managing the podling's brand / trademarks?

Yes.

Signed-off-by:

(pegasus) Duo Zhang
Comments:
(pegasus) Liang Chen
Comments:
(pegasus) Von Gosling
Comments:
(pegasus) Liu Xun
Comments:

Release our latest RC

Initial setup
Working towards first release
Community building
Nearing graduation
Other:

(resilientdb) Junping Du
Comments:
(resilientdb) Kevin Ratnasekera
Comments:
(resilientdb) Jean-Baptiste Onofré
Comments: The podling did a good job in the release, but waiting for a third binding vote on general@. That's not good regarding the effort of the podling and very active/responsive podling. We sent reminder on the mailing list, but it didn't help yet. I'm a bit concerned by the number of active IPMC members recently.

IPMC/Shepherd notes:

Justin Mclean: Project contacted about adding/replacing mentors and about what is stopping them from graduating.

Page tree

Timeline

Shepherd Assignments