Incubator PMC report for February 2026

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

TODO add narrative

Community

New IPMC members:

People who left the IPMC:

New Podlings

Podlings that failed to report, expected next month

Graduations

• list podling heres

The board has motions for the following:

• Your podling here?

Releases

The following releases entered distribution during the month of January:

IP Clearance

Legal / Trademarks

Infrastructure

Miscellaneous

Credits

Table of Contents

Burr
Caldera
Cloudberry
Fesod
GeaFlow
GraphAr
Hamilton
HoraeDB
Seata
Texera
Toree
XTable

Burr

Burr is a lightweight in-process python framework that standardizes the expression and execution of state machines as action-driven graphs, while making graph execution easily observable. It is particularly suited for AI agent workflows, simulations, and other dynamic systems, and comes with a self-hostable observability UI that integrates with OpenTelemetry.

Burr has been incubating since 2025-05-24.

Three most important unfinished issues to address before graduating:

1. Build release cadence.
2. Add a couple more core contributors.
3. Get more focused on building community.

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

N/A

How has the community developed since the last report?

1. Discord seeing small growth.
2. Otherwise largely feels flat-ish.

How has the project developed since the last report?

1. We have just managed to get our first release out!
2. We're looking forward to

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-01-24

When were the last committers or PPMC members elected?

2025-05-24.

Have your mentors been helpful and responsive?

Are things falling through the cracks? If so, please list any open issues that need to be addressed.

Yes. They helped us figure out a first version release process.

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

Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?

Nothing here that we're aware of.

Signed-off-by:

•  (burr) Kevin Ratnasekera
  Comments:
•  (burr) Ayush Saxena
  Comments:
•  (burr) PJ Fanning
  Comments:
•  (burr) Jarek Potiuk
  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?

Are things falling through the cracks? If so, please list any open issues that need to be addressed.

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

Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?

Caldera name approved.

Signed-off-by:

•  (caldera) Kevin Ratnasekera
  Comments:
•  (caldera) Francis Chuang
  Comments:
•  (caldera) PJ Fanning
  Comments: Very early days. SGA not ready yet. Mailing lists not really active yet.
•  (caldera) Gordon King
  Comments:

IPMC/Shepherd notes:

Cloudberry

Cloudberry is an advanced and mature open-source Massively Parallel Processing (MPP) database, derived from the open-source version of Pivotal Greenplum Database®️ but built on a more modern PostgreSQL 14 kernel, whereas Greenplum is based on PostgreSQL 12. This upgrade brings enhanced enterprise capabilities, making Cloudberry well-suited for data warehousing, large-scale analytics, and AI/ML workloads.

Cloudberry has been incubating since 2024-10-11.

Three most important unfinished issues to address before graduating: 

1. Grow the contributor and community to ensure long-term sustainability.
2. Publish a few more Apache releases following the ASF release processes.

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?

• Mailing list Activity: 82 new emails on the Dev mailing list since the last report, covering community, repositories, support, technical and Apache-related discussions.
• GitHub Discussions: 5 new threads since last report.
• New Committers: Rose Duan
• Events:
  • Hosted a Cloudberry community booth at the China Open Source Conference (COSCon'25) in Beijing, Dec 6-7, 2025.
  • Apache Cloudberry Meetup organized in Shenzhen: 30+ attendees on Jan 17th
  • Commenced Apache Cloudberry Bi-weekly Community Meeting, see details in https://s.apache.org/9ba4d, the 1st meeting was held on January 30, 2026.

How has the project developed since the last report?

• PostgreSQL Kernel upgrade (14~>16): at this stage, most of the core enablement work for PostgreSQL 16.9 has been completed. Currently addressing Cloudberry schedule tests.
• Performance
  • PAX: optimize I/O read for multiple discrete columns in a group.
  • Add UDP2 interconnect protocol implementation (right now it is still an experimental feature).
  • Set join_collapse_limit default value to 13.
• Stability
  1. Merged 72 commits, most of them - bugfixes and CI/CD improvements.
  2. Fixed 2 CVEs.
• CI and infra
  1. Added support for Ubuntu 22.04 and Debian packages to CI/CD
  2. Added support for Rocky Linux 8 to CI/CD
• Sub-repositories:
  • cloudberry-pxf. After several months of continuous effort, the PXF project has recently achieved a significant milestone:
    1. The code baseline has been 100% aligned with the archived pxf-archive from GP.
    2. Completed full adaptation for Cloudberry.
    3. Added a relatively comprehensive and extensive CI pipeline for PXF.
    4. Source code cleanup is in progress.
  • Squash cloudberry-bootcamp repository into devops/sandbox in the main repository catalog.
• New release: 2.1
  • Merged 244 commits from main to REL_2_STABLE. We're ready to release Cloudberry 2.1.
• Ecosystem
  1. Madlib integration is still in progress. We successfully performed manual tests, but PR is still open to fix the CI bugs: https://github.com/apache/madlib/pull/627.
  2. Working on diskquota extension integration: still in progress - see https://github.com/apache/cloudberry/pull/1490.
• 2025 Summary and 2026 Overview discussions
  1. Published Cloudberry 2025 Review blog post: https://s.apache.org/fxde8
  2. Initiated Cloudberry 2026 roadmap discussions: https://s.apache.org/jxd7s

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:

• August 25, 2025

When were the last committers or PPMC members elected?

• Rose Duan, 19th Jan 2026

Have your mentors been helpful and responsive?

Yes.

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

Yes.

Signed-off-by:

•  (cloudberry) Roman Shaposhnik
  Comments:
•  (cloudberry) Willem Ning Jiang
  Comments:
•  (cloudberry) Kent Yao
  Comments:

IPMC/Shepherd notes:

Fesod

Fesod is a high-performance and memory-efficient Java library for reading and writing Excel files, designed to simplify development and ensure reliability.

Fesod has been incubating since 2025-09-17.

Three most important unfinished issues to address before graduating:

1. Ensure that the website and codebase are fully compliant with ASF policies.
2. Add more core contributors.
3. Get more focused on building community.

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

N/A

How has the community developed since the last report?

1. We have a discussion on private mail list about voting first committer.
2. The project now has several active contributors.

How has the project developed since the last report?

1. We have already released our first version(2.0.0-incubating).
2. Since some error in 2.0.0-incubating, we are now voting for 2.0.1-incubating.
3. The new contributors still contribute for project.

How would you assess the podling's maturity?

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

Date of last release:

2026-01-21

When were the last committers or PPMC members elected?

N/A

Have your mentors been helpful and responsive?

Yes. We truly thanks our mentors' help in voting process.

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

 Yes. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-246

Signed-off-by:

•  (fesod) tison
  Comments:
•  (fesod) Dave Fisher
  Comments:
•  (fesod) Huajie Wang
  Comments:
•  (fesod) PJ Fanning
  Comments:

IPMC/Shepherd notes:

GeaFlow

GeaFlow is a streaming graph computing engine for distributed large-scale real-time graph storage and analysis. It supports trillion-level graph storage, hybrid graph and table processing, real-time/offline graph computing, and interactive graph analysis.

GeaFlow has been incubating since 2025-06-06.

Two most important unfinished issues to address before graduating:

1. Cultivate a more diverse community by engaging contributors and committers from varied organizations and global regions.
2. Implement predictable release cycles and maintain high project stability to encourage broad participation and adoption.

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 GeaFlow community has maintained its core contributor base over the past month, with existing contributors continuing to drive development. The community has remained active with ongoing contributions including new features, optimizations, and bugfix. Additionally, several PRs are currently under review.

How has the project developed since the last report?

Over the past month, the GeaFlow project has focused on feature enhancements, optimizations, and dependency updates. Key changes are including:

• Add ISO-GQL PROPERTY_EXISTS predicate(#702).
• Adding Lucene & Embedding-Based Search Operators for LightWeight Context GraphMemory(#716).
• Fix memory management in mmap_ipc.cpp(#725).
• Support Graph Consolidate algorithm and added GraphMemory Java Server and Client(#729).

These updates reflect ongoing progress in graph-related functionality expansion, code quality improvements, and Graph+AI capabilities.

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:

The last version was released on November 19, 2025.  

When were the last committers or PPMC members elected?

The last committers were elected on January 4, 2026.

Have your mentors been helpful and responsive?

Yes, we have received helpful guidance.

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

N/A.

Signed-off-by:

•  (geaflow) Willem Ning Jiang
  Comments:
•  (geaflow) Xin Wang
  Comments:
•  (geaflow) Jingsong Lee
  Comments:
•  (geaflow) Paul Klingelhuber
  Comments:
•  (geaflow) Justin Mclean
  Comments:

IPMC/Shepherd notes:

GraphAr

GraphAr is an open-source and language-independent data file format designed for efficient graph data storage and retrieval.

GraphAr has been incubating since 2024-03-25.

Three most important unfinished issues to address before graduating:

1. Attract more committers, contributors, and users to grow the community.   2. Release more versions compliant with ASF standards.

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

None.

How has the community developed since the last report?

1. a new contributors have had their PRs merged.
2. Communicate and cooperate with LEX (LDBC Extended GQL Schema) in the graph YAML scheme

How has the project developed since the last report?

1. Merged 19 PRs since the last report.
2. Added rust module
3. Improved python SDK

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-08-29

When were the last committers or PPMC members elected?

2025-07-14

Have your mentors been helpful and responsive?

Are things falling through the cracks? If so, please list any open issues that need to be addressed.

The mentors are very helpful and responsive.

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

Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?

There are no known brand and naming issues.

Signed-off-by:

•  (graphar) Calvin Kirs
  Comments:
•  (graphar) tison
  Comments:
•  (graphar) Xiaoqiao He
  Comments:
•  (graphar) Yu Li
  Comments:

IPMC/Shepherd notes:

Hamilton

Hamilton is a lightweight in-process framework to define, execute, and observe directed acyclic graphs (DAGs) that express data transformations. In Hamilton, one can express complex DAGs of transformations, e.g. from dataframe transformations (using pandas, polars, PySpark), machine learning pipelines, through to regular software engineering API request and LLM API based workflows. Observability hooks are built into the framework. The Hamilton UI is a self-hostable service to capture observability output from workflow runs.

Hamilton has been incubating since 2025-04-12.

Three most important unfinished issues to address before graduating:

1. Release all the packages under Apache.
2. Build release cadance.
3. Build community.

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

N/A

How has the community developed since the last report?

Feels flat-ish. But new contributors keep passing through.

How has the project developed since the last report?

We managed to get our first release out. Otherwise guiding new contributors that want to help with issues.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

•  Initial setup
•  Working towards first releases [we've done 1 package, 4 more to go].
•  Community building
•  Nearing graduation
•  Other:

Date of last release:

2025-10-09

When were the last committers or PPMC members elected?

2025-04-12

Have your mentors been helpful and responsive?

Are things falling through the cracks? If so, please list any open issues that need to be addressed.

All good. Nothing outstanding right now.

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

Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?

Not aware of any issues.

Signed-off-by:

•  (hamilton) Kevin Ratnasekera
  Comments:
•  (hamilton) Ayush Saxena
  Comments:
•  (hamilton) PJ Fanning
  Comments:
•  (hamilton) Jarek Potiuk
  Comments:

IPMC/Shepherd notes:

HoraeDB

HoraeDB is a high-performance, distributed, cloud native time-series database.

HoraeDB has been incubating since 2023-12-11.

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?

Are things falling through the cracks? If so, please list any open issues that need to be addressed.

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

Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?

Signed-off-by:

•  (horaedb) tison
  Comments: Pending for retriement.
•  (horaedb) Shaofeng Shi
  Comments:
•  (horaedb) Gang Li
  Comments:
•  (horaedb) Von Gosling
  Comments:

IPMC/Shepherd notes:

Seata

Seata(Simple Extensible Autonomous Transaction Architecture)is an easy-to- use and high-performance distributed transaction solution, used to solve the data consistency problem.

Seata has been incubating since 2023-10-29.

Three most important unfinished issues to address before graduating:

1. Complete the transfer of Seata's existing trademarks to ASF. After several rounds of communication, we have not reached an agreement on the trademark issue yet.

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

1. We hope to sign an additional memorandum with the ASF counsel team for the trademark transfer process within Ant Group.

How has the community developed since the last report?

1. 27 new code contributors have joined the community (649 contributors in total).
2. 6 new committers were elected.
3. We participated in the China Open Source Conference event and introduced the community progress of Apache Seata.

How has the project developed since the last report?

1. Since the last report, we've merged 204 PRs, which included multiple AI-related features.
2. Since the last report, We've fixed some of the reported vulnerabilities and fixed more than 59 dependency vulnerabilities.

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-10-06

When were the last committers or PPMC members elected?

  2026-01-04

Have your mentors been helpful and responsive?

Are things falling through the cracks? If so, please list any open issues that need to be addressed.

Our mentors have been very helpful and responsive.

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

Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?

No Trademark issues.

Signed-off-by:

•  (seata) Sheng Wu
  Comments:
•  (seata) Justin Mclean
  Comments:
•  (seata) Huxing Zhang
  Comments: The podling needs sometime to finish trademark transfer. Otherwise it is all good.
•  (seata) Heng Du
  Comments:
•  (seata) Xin Wang
  Comments:

IPMC/Shepherd notes:

Texera

Texera is an open-source system to support collaborative data science, AI, and ML using GUI-based workflows. Our vision is to develop a system to support cloud platforms on which users can easily analyze data and use AI/ML techniques provided as operators. Users with various backgrounds, irrespective of whether they know coding or not, can collaborate on the same project to construct a pipeline. Experienced users can use programming languages such as Python, R, Java, and Scala to implement customized computation logic. The platform allows users to pause the execution of a workflow to investigate the operator states, and resume the execution at a later time. The platform can be used by a research community to publish valuable resources such as data sets, workflows, and ML models to share their domain-specific knowledge and support reproducibility of scientific research. The platform also allows users to elastically request computing resources from public clouds for computationally-intensive tasks.

Texera has been incubating since 2025-04-12.

Three most important unfinished issues to address before graduating:

1. Regularize Apache Releases: Finalize the release process for v1.1.0-incubating, ensuring all licensing requirements (Whimsy checks) are met, and establish a consistent release cadence.

2. Community Growth & Diversity: Continue expanding the active contributor base beyond the initial research group to ensure a diverse, self-sustaining community (as evidenced by recent external contributors).

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?

We have welcomed contributions from several new developers including Victor Fawole, GitHub user "LJX2017", and Carlos Ernesto Alvarez Berumen.

How has the project developed since the last report?

Added ML training operators for linear and logistic regression and a Choropleth map operator for visualization.

Implemented support of Large Binary (single binary row with more than 2GB data) to handle larger datasets efficiently.

Introduced a Materialized Execution Mode.

Improved Multipart Uploads by redirecting them through the File Service and adding resumable upload support.

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-12-08 (tagged on Github)

When were the last committers or PPMC members elected?

No new PPMC members or committers were elected during this reporting period.

Have your mentors been helpful and responsive?

Yes, mentors have been extremely helpful. Thanks to Ian Maxon, he attends monthly sync meetings and helped a lot on release process and security issues, and also thanks to PJ, he migrated our application from Akka to Pekko for license compliance and actively monitors our code base.

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

Yes. The PPMC is actively working on the texera.apache.org website setup and has been auditing license headers and artifact naming to comply with ASF branding and Whimsy requirements.

Signed-off-by:

•  (texera) Cezar Andrei
  Comments:
•  (texera) Gordon King
  Comments:
•  (texera) PJ Fanning
  Comments:
•  (texera) Ian Maxon
  Comments: It might be good in the project status to mention how the new contributors are helping with the project

IPMC/Shepherd notes:

Toree

Toree provides applications with a mechanism to interactively and remotely access Apache Spark.

Toree has been incubating since 2015-12-02.

Three most important unfinished issues to address before graduating:

None

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

None, Nothing much of news from previous report

How has the community developed since the last report?

The community is actively working on Release 0.6 review feedback and enhancing some of the legal and branding aspects of the release aiming to be fully compliant with graduated requirements. The new release brings Scala 2.13 and Spark 3.4.4 support.

How has the project developed since the last report?

Release 0.6.0 preparation and votes New members joining the community

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:

2022-04-11

When were the last committers or PPMC members elected?

• PJ Fanning was added to the PPMC on 2025-11-10

Have your mentors been helpful and responsive?

Note applicable

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

No trademark issues

IPMC/Shepherd notes:

Signed-off-by:

•  (toree) Luciano Resende
  Comments:  The podling should push graduation after release is out process   - [ ] (toree) Ryan Blue
  Comments:
•  (toree) Weiwei Yang
  Comments:

IPMC/Shepherd notes:

XTable

XTable is an omni-directional converter for table formats that facilitates interoperability across data processing systems and query engines.

XTable has been incubating since 2024-02-11.

Three most important unfinished issues to address before graduating:

1. Strengthening community building by actively engaging with users.
2. Increasing adoption by implementing key features planned - Deletion Vectors, Data Governance interoperability for catalogs, Supporting new Table Formats.
3. Fixing packaging issues for bundled jars for new features.

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?

1. 5 unique contributors have made commits during this period.
2. Community continues working collaboratively on major features like Paimon source support and Delta Kernel support.

How has the project developed since the last report?

1. Apache Paimon conversion source support landed and enhanced with incremental sync.
2. Delta Kernel APIs implementation in progress (major milestone).
3. Bug fixes for Delta-to-Iceberg conversion with column mapping.
4. Improved handling of edge cases (empty tables, nested field stats).

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-06-04 (0.3.0-incubating)

When were the last committers or PPMC members elected?

2025-11-09

Have your mentors been helpful and responsive?

Our mentors have been helpful and responsive.

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

No answer.

Signed-off-by:

•  (xtable) Jesús Camacho Rodríguez
  Comments:
•  (xtable) Stamatis Zampetakis
  Comments:
•  (xtable) Jean-Baptiste Onofré
  Comments: I would suggest to try to speed up the release pace. I would also be happy to help to create momentum.

IPMC/Shepherd notes: