DRAFT DRAFT DRAFT
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:
Keep all lines under 76 characters long.
All content under the ### headings should be indented by two spaces. Do not use tabs.
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.
fold -w 76 -s $1 | cat -s |
Wed May 06 | Podling reports due by end of day |
Sun May 10 | Shepherd reviews due by end of day |
Sun May 10 | Summary due by end of day |
Tue May 12 | Mentor signoff due by end of day |
Wed May 13 | Report submitted to Board |
Wed May 20 | Board meeting |
| Calvin Kirs | Calvin Kirs |
| Dave Fisher | Caldera |
| Dave Fisher | Texera |
| Drew Farris | Toree |
| Drew Farris | XTable |
| Justin Mclean | Casbin |
| P. Taylor Goetz | Cloudberry |
| P. Taylor Goetz | GeaFlow |
| PJ Fanning | GraphAr |
| Timothy Chen | Fesod |
| Willem Jiang | Burr |
| Willem Jiang | Hamilton |
| Xuanwo | Seata |
# Incubator PMC report for May 2026
The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.
There are currently 28 podlings under incubation. In April, the Incubator made 6 releases, and some release votes are currently underway. There were two additions and no removals to IPMC membership.
Mailing list discussion in April focused primarily on release voting activity. There was also a discussion about using MCP-based tooling with publicly available data to generate Incubator insights, which sparked interest on the mailing list. This tooling was subsequently used, with human oversight, to help produce this report. A new incubation proposal for PIC Standard was discussed. A graduation discussion for Apache Livy has started.
Caldera has shown very limited engagement with ASF since entering incubation. Project communication has not been taking place on the mailing lists, and initial setup tasks, including ICLAs, accounts, and SGA progress, have not been progressing visibly. The IPMC raised these concerns with the project, and the podling has confirmed it will change course to address them and is making progress.
Casbin is a new podling (entered February 2026) submitting its first report. Development activity still appears to be primarily occurring outside ASF infrastructure, and project discussions are taking place on Discord and GitHub Discussions rather than on the mailing lists. The IPMC will monitor this.
OpenServerless has been incubating for nearly two years and has not yet released an ASF release. Mailing list activity is almost entirely automated GitHub messages. No new committers or PPMC members have been elected since August 2024, and a private message sent to the podling about one month ago has not received a response. Mentor comments in the most recent reports and on the general list directly reflect these concerns. The IPMC has raised the question of whether to initiate a discussion about retirement. OpenServerless has started to move towards marking a release.
OzHera has not made an ASF release in over a year despite ongoing development activity. The project has been asked to outline the current status of release preparation, what is blocking the next release, and to address low mentor engagement across recent reporting periods.
PouchDB has been in incubation for 12 months with no ASF release. The project website at pouchdb.apache.org needs some work (which looks to have been done), and the previous project site at pouchdb.com still exists where it shouldn't. The IPMC raised these issues with the project's mentors, and the project is working to address them.
The IPMC continues to monitor long-running podlings and will follow up on any release or community concerns as needed. In particular, Toree has been incubating since December 2015. The project is actively working through release candidate iterations and plans to push for graduation once the release completes.
## Community
### New IPMC members:
- Jark Wu
- Russell Spitzer
### People who left the IPMC:
- No one
## New Podlings
- None
## Podlings that failed to report, expected next month
- TODO
## Graduations
- None
The board has motions for the following:
- None
## Releases
The following releases entered distribution during the month of
April:
- Cloudberry 2.1.0
- Fluss-rust 0.1.0
- Hamilton 1.90.0
- Iggy 0.8.0
- KIE 10.2.0
- ResilientDB 1.12.0
## IP Clearance
- None
## Legal / Trademarks
N/A
## Infrastructure
N/A
## Table of Contents
[Burr](#burr)
[Caldera](#caldera)
[Casbin](#casbin)
[Cloudberry](#cloudberry)
[Fesod](#fesod)
[GeaFlow](#geaflow)
[GraphAr](#graphar)
[Hamilton](#hamilton)
[Pony Mail](#pony mail)
[Seata](#seata)
[Texera](#texera)
[Toree](#toree)
[XTable](#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. Complete second Apache release (0.42.0-incubating) — vote on incubator general currently in progress.
2. Diversify reviewer base — reviewer diversity (effective # 1.87) is concentrated; need more independent reviewers for PRs
3. Grow independent committer base — currently 3 active committers with commit activity (skrawcz, ebenizzy, and community contributors); need to identify and elect new committers from active
contributors
### 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?
• 7 new contributors in the last 3 months, 14 over 6 months
• 12 unique committers active in the 3-month window
• 10 unique PR authors and 6 unique reviewers (sampled)
• dev@ mailing list has 12 unique posters
• Active participation in release votes from mentors (Jernej Frank, PJ Fanning, Jarek Potiuk) and community members
• André Ahlert added as collaborator and leading UI contributions (16 commits since Jan 2026)
### How has the project developed since the last report?
• First official Apache release (0.41.0-incubating) completed and published to dist.apache.org (~January 2026)
• 0.42.0-incubating RC3 vote in progress (started April 26); RC1 and RC2 received constructive feedback on licensing which was addressed
• New features: AWS Bedrock integration (#677), cloud-native AWS deployment example (#666), ecosystem page for website (#661), flexible_api decorator for mypy compatibility (#683), async persister
improvements (#681), graceful stream shutdown (#680)
• CI/infrastructure improvements: repo governance workflows, release validation pipeline, automated artifact verification
• 34 issues closed since January 2026; 58 commits in 3-month window
• Median PR time-to-merge: 2.4 days
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [x] Initial setup
- [x] Working towards first release
- [x] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2026-01-25
### When were the last committers or PPMC members elected?
No new committers or PPMC members have been elected since the initial roster was established (last LDAP modification: 2025-10-22). One active contributor André Ahlert is a candidate for election.
### 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.
Not aware of any issues.
### 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:
- [ ] (burr) Kevin Ratnasekera
Comments:
- [ ] (burr) Ayush Saxena
Comments:
- [x] (burr) PJ Fanning
Comments: Need to look at adding extra committers from the active contributors.
- [ ] (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:
1. Caldera GitHub repository needs to be transferred
2. Apache Caldera website needs to be stood up
3. Community growth
### Are there any issues that the IPMC or ASF Board need to be aware of?
- Awaiting response from Apache infra team for GitHub repository transfer
### How has the community developed since the last report?
- Caldera Discord community growing ~500 users
- Caldera GitHub community actively submitting PRs
- GitHub stars reached 6.9k
### How has the project developed since the last report?
- Preparing for GitHub repository transfer to ASF
- Approved 5 PRs from contributors
- Caldera WIKI created. Link: cwiki.apache.org/confluence/display/CALDERA
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [x] Initial setup
- [ ] Working towards first release
- [x] Community building
- [ ] Nearing graduation
- [x] Other: Awaiting repository transferring (May 20th).
### Date of last release:
N/A
### When were the last committers or PPMC members elected?
at founding/incubation
### 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
### 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 known brand or naming issues. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-248 approved.
### Signed-off-by:
- [ ] (caldera) Kevin Ratnasekera
Comments:
- [x] (caldera) Francis Chuang
Comments: There were some delays with getting the project into the incubator, but the PPMC has made significant progress in the last few months to get the ball rolling.
- [x] (caldera) PJ Fanning
Comments: There was talk of adding some new named PPMC members but the discussion has not been made official on the private list.
- [ ] (caldera) Gordon King
Comments:
### IPMC/Shepherd notes:
--------------------
## Casbin
Casbin is a powerful, efficient open-source access control framework offering a unified, model-driven authorization approach. Based on the PERM (Policy, Effect, Request, Matchers) metamodel and its domain-specific language (DSL), Casbin seamlessly integrates ACL, RBAC, and ABAC models to enable flexible and fine-grained policy management. It delivers high-performance access control enforcement and supports a comprehensive multi-language ecosystem including Go, Java, Node.js, Python, .NET, C++, and Rust. Apache Software Foundation incubation will establish Casbin as a community-driven, standardized authorization solution.
Casbin has been incubating since 2026-02-07.
### Three most important unfinished issues to address before graduating:
- Establish a clear release process aligned with ASF guidelines and perform the first official Apache release.
- Grow the community by onboarding new contributors from diverse organizations and transitioning discussions to Apache mailing lists.
- Complete the formal transfer of domains and trademarks 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?
- Officially announced Casbin's acceptance into the Apache Incubator and published the news via project blogs and community channels
- Raised community activity: a new group of developers have joined the discussions on Discord and GitHub Discussions
- Maintained steady growth in GitHub stars (the main repository increased from 19.4k to 20.1k)
- During the incubation period, the download volume of packages across all language versions has kept rising, with the overall ecological adoption growing steadily
- dev@casbin.apache.org saw 44 emails (mostly Dependabot bot notifications), including a community discussion proposal, with new subscribers joining.
### How has the project developed since the last report?
- This is the first official monthly report for Casbin following its admission to the Apache Incubator
- Added standardized configuration files and optimized the project's overall configuration management system
- Implemented ASF compliance requirements: added the official .asf.yaml configuration file and Apache disclaimer file to ensure the project is fully compliant with the foundation's norms
- Completed the addition of standard Apache License 2.0 headers to the entire codebase and initiated the preliminary intellectual property transfer process to the ASF
- A total of 30 PRs merged and 40 issues closed during the incubation period
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
No apache release yet.
### When were the last committers or PPMC members elected?
2026-02-07
### Have your mentors been helpful and responsive?
Yes, 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?
Name is approved:
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-251
### Signed-off-by:
- [ ] (casbin) Hao Ding
Comments:
- [ ] (casbin) Huajie Wang
Comments:
- [ ] (casbin) Hulk Lin
Comments:
- [ ] (casbin) Jerry Shao
Comments:
- [x] (casbin) Zili Chen
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?
- The community continued the Apache Cloudberry bi-weekly community
meeting, holding five public meetings from February to April 2026. These
meetings covered release coordination, kernel upgrades, ecosystem projects,
testing strategy, events, and open community topics.
- New Committers: Xiaoyu Liu (@misterRaindrop), Nikolay Antonov
(@ostinru), Robert Mu (@robertmu)
- New PPMC Member: Leonid Borchuk
- Community channels:
- Created a new Slack workspace and a new Discord server after the
previous Slack workspace became unavailable.
- Updated the website and planned updates across related repositories
to point users to the current communication channels.
- Governance and community process:
- Started discussion on an AI conduct policy to guide responsible use
of LLM tools while following ASF copyright and attribution expectations.
- Added a website page documenting how to invite new PPMC members.
- Events and outreach:
- Community Over Code Asia 2026: around 11 Cloudberry-related
proposals, now waiting for the review results. Plan to organize one
in-person community gathering in Beijing during the conference.
- A Cloudberry meetup was organized in Moscow, with public recordings
and a Russian Habr article bringing more user feedback to the community.
- Two community members were confirmed as PGConf.dev 2026 speakers.
- New contributors appeared in community discussions and PRs, including
contributions around Cloudberry Backup, PXF, and core repository features.
### How has the project developed since the last report?
- Released Apache Cloudberry (Incubating) 2.1.0 in April 2026, the
project's second Apache release after entering the ASF Incubator.
Convenience RPM/DEB packages and binary packages were provided for the
first time. Manual packages were made for 2.1.0, and automation is being
considered for 2.2.0.
- PostgreSQL kernel upgrade:
- Started the PostgreSQL 14.x minor-version upgrade work for the 2.x
release branch. The branch progressed from PostgreSQL 14.4 through 14.8,
with later 14.x updates being tracked in the project Kanban.
- Continued the PostgreSQL 16 kernel upgrade on the work development
branch. This work is expected to be completed by the end of Q2 2026.
- Fixed PostgreSQL upstream CVEs and security-related patches,
including libpq SSL/GSS negotiation error handling.
- Core project improvements:
- Merged the diskquota extension into the main repository.
- Added the gp_stats_collector extension, improving observability and
laying groundwork for dashboard related work.
- Added AQUMV exact-match support for multi-table JOIN queries.
- Started discussion on an Iceberg subsystem for `datalake_fdw`.
- CI, testing, and platform support:
- Added Ubuntu 24.04 Docker image and test matrix support.
- Continued Rocky Linux 10 support work, with initial build docker
images. The related test matrix support is to be added.
- Started discussion on rethinking the testing strategy for better test
efficiency and coverage.
- Upgraded Go to 1.24 in Cloudberry development images and related
ecosystem repositories. Newer Go version support is in the discussion.
- Started adding Behave tests for gpMgmt tools (WIP).
- Ecosystem and sub-repositories:
- `cloudberry-pxf`:
- Started a roadmap discussion for the PXF project.
- Released 2.1.0, the first Apache release for PXF.
- Renamed Java packages from `org.greenplum` to
`org.apache.cloudberry` and updated ASF compliance files.
- Added Java 17 support and Rocky Linux 9 CI support.
- Removed `gradle-wrapper.jar` from source release artifacts and
download/verify it during build for ASF license compliance.
- Added or improved JDBC tests using Testcontainers for ClickHouse,
MS SQL, and Oracle.
- Upgraded dependencies including Apache AVRO, Apache ORC, Parquet,
and HBase related components, and discussed Java 21 support.
- `cloudberry-backup`:
- Released 2.1.0, the first Apache release for gpbackup.
- Completed migration work from legacy Concourse CI to GitHub Actions.
- Added ASF release script support and Cloudberry 2.1 compatibility.
- Started a roadmap discussion for the backup project.
- Merged gpbackman-related backup management work. The Prometheus
exporter for the gpbackup history database work is in the review process.
- `cloudberry-go-libs`:
- Tracked a security issue and dependency update needed by related
backup tooling.
- Apache MADlib:
- Continued collaboration with Apache MADlib to add Apache Cloudberry
support upstream, with community discussion ongoing. See:
https://s.apache.org/bsu9m
- Next release: Started early discussion for Apache Cloudberry 2.2.0,
including release manager, release process documentation, packaging
automation, and testing strategy.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [x] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
- April 14, 2026 - Apache Cloudberry (Incubating) 2.1.0
### When were the last committers or PPMC members elected?
- March 24, 2026 - Xiaoyu Liu (@misterRaindrop), Nikolay Antonov
(@ostinru), Robert Mu (@robertmu) were announced as new committers.
- April 07, 2026 - Leonid Borchuk was announced as a new PPMC member.
### 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 discussed and voted to approve two new committers.
2. As the community has begun to become more organized, the number of contributors is growing steadily.
### How has the project developed since the last report?
1. we discussed some future core roadmap plans on the mailing list;
2. We plan to release the second version of the incubator around June;
3. In addition to developing new features, we are also working on enhancing the project's foundational tools.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2026-02-11
### When were the last committers or PPMC members elected?
2026-04-22
### Have your mentors been helpful and responsive?
Yes. We truly thanks our mentors' help in daily guidance and reminders.
### Is the PPMC managing the podling's brand / trademarks?
Yes. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-246
### Signed-off-by:
- [x] (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. Currently, the community is actively advancing the development of Graph Memory, aiming to serve as the underlying infrastructure for Agent Memory.
GeaFlow has been incubating since 2025-06-06.
### Three 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.
Furthermore, multiple community contributors are actively participating in CoC Asia 26, which will be held in Beijing, China, and have prepared multiple proposals for the associated Incubator, Streaming, and Data+AI tracks.
### How has the project developed since the last report?
Over the past month, the GeaFlow project has continued its progress with a focus on code robustness, dependency management, and community facilitation. Key developments include:
- Introduced the CONTRIBUTING.md file to outline contribution guidelines, facilitating easier onboarding for new developers (#765).
- Enhanced code stability by adding checks for empty search results to prevent array out of bounds errors (#769) and handling null/empty inputs in average methods (#760).
- Optimized code quality by defining the BYTES_PER_KB constant for consistency (#770), replacing raw type usage with type-safe methods (#766), and excluding conflicting lucene-core dependencies (#778).
- Improved CI infrastructure by formatting build and test commands for better readability (#763).
- New pull requests were opened targeting production GCN inference pipelines, hot-reload mechanisms, and vector implementation, indicating active development in AI capabilities and architecture optimization.
These updates demonstrate continued advancement in codebase health, project infrastructure stability, and the expansion of Graph+AI features.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] 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:
- [x] (geaflow) Xin Wang
Comments:
- [ ] (geaflow) Jingsong Lee
Comments:
- [ ] (geaflow) Paul Klingelhuber
Comments:
- [X] (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 completed PR merge
2. Add two new Committers
### How has the project developed since the last report?
1. Merged 37 PRs since the last report.
2. Rust module: added GraphInfo support, enabled Rust build on macOS and updated Arrow linking.
3. C++ library code quality improvements: added clang-tidy/clang-format integration, enforced strongly-typed enums (enum class), enabled -Wall -Werror -Wextra compilation flags, removed unused variables and headers, and used std::move to reduce copies.
4. Refactored CMake build system: restructured CMake files into subdirectories, added ccache support for faster builds, added pre-commit hooks and commit message validation.
5. CI/CD improvements: enabled macOS CI, replaced make with ninja, added ccache support, validated PR titles, and switched to ubuntu-slim runners.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [x] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2025-08-29
### When were the last committers or PPMC members elected?
2026-04-22
### 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:
- [x] (graphar) tison
Comments:
- [ ] (graphar) Xiaoqiao He
Comments:
- [ ] (graphar) Yu Li
Comments:
### IPMC/Shepherd notes:
[PJF] Maybe time to start thinking about Graduation (incubating for 2 years). Dev list mail traffic is very low but it does seem like podling is fairly active generally.
--------------------
## 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. **Grow reviewer/committer diversity** — Bus factor proxy is 2/3 (50%/75% of commits). Need to cultivate more regular reviewers beyond the core 2-3 maintainers. Reviewer diversity (effective #) is 1.68, which needs improvement.
2. **Establish a regular release cadence** — Two incubating releases to date (v1.89.0 in Oct 2025, v1.90.0 in Apr 2026). Need to demonstrate a sustainable, community-driven release process.
3. **Complete package rename from sf-hamilton to apache-hamilton** — Migration from the legacy `sf-hamilton` PyPI package to `apache-hamilton` is in progress (PR #1561). This is important for brand independence and Apache compliance.
### 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?
- 8 new contributors in the last 3 months
- 12 unique PR authors, 7 unique reviewers (sampled) in the 3-month window
- 13 unique committers in the last 3 months
- dev@ mailing list: 33 messages from 9 unique posters
- Active community PRs from external contributors (ddtrace upgrade, datasaver fix, async typing fix, optional extractors feature, docs fixes)
- PR activity strong: 97 opened / 72 merged in 3 months, median merge time 8 days
### How has the project developed since the last report?
- **Released apache-hamilton v1.90.0-incubating** (April 2026) — second Apache release
- Ongoing package rename from `sf-hamilton` to `apache-hamilton` across codebase, docs, and PyPI
- Plugin upgrades (Datadog ddtrace 4.x migration)
- Bug fixes for `from __future__ import annotations` compatibility
- Typing improvements (fluent builder pattern with `Self`)
- New feature: optional flag for `from_` data loaders
- Dependency maintenance: security bumps for dompurify, django, follow-redirects, protobufjs, vite, lodash
- Continued growth in external contributor PRs
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [x] Initial setup
- [x] Working towards first release
- [x] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2026-04-25
### When were the last committers or PPMC members elected?
- At founding
### 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.
I haven't asked yet, but better docs on docker build guidance would be appreciated.
### 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 that we're aware of.
### Signed-off-by:
- [ ] (hamilton) Kevin Ratnasekera
Comments:
- [ ] (hamilton) Ayush Saxena
Comments:
- [x] (hamilton) PJ Fanning
Comments: Need to look at adding extra committers from the active contributors.
- [ ] (hamilton) Jarek Potiuk
Comments:
### IPMC/Shepherd notes:
--------------------
## Pony Mail
Pony Mail is a mail-archiving, archive viewing, and interaction service,
that can be integrated with many email platforms.
Pony Mail has been incubating since 2016-05-27.
### Three most important unfinished issues to address before graduating:
1.
2.
3.
### 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:
- [ ] (ponymail) John D. Ament
Comments:
- [ ] (ponymail) Dave Fisher
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. We have completed the signing of the Trademark Transfer Consent and POA documents and are currently awaiting further response from the ASF counsel team.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No issues at the moment.
### How has the community developed since the last report?
1. 32 new code contributors have joined the community (681 contributors in total)
2. 1 new committers and 2 new PPMC members were elected.
3. We have submitted proposals for 2 GSoC projects and submitted 3 topic proposals for Community over Code Asia.
### How has the project developed since the last report?
1. Since the last report, we have merged 77 PRs, primarily including several new architectural evolution features.
2. Since the last report, we have published two ASF releases: seata-2.6.0 and seata-go 2.1.0.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2026-03-12
### When were the last committers or PPMC members elected?
2026-04-30
### 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:
- [ ] (seata) Heng Du
Comments:
- [x] (seata) Xin Wang
Comments:
### IPMC/Shepherd notes:
--------------------
## Texera
Texera is an open-source platform for human-AI collaborative data science using visual workflows. It enables human analysts to construct, execute, and refine data analysis tasks through an intuitive GUI, assisted by AI agents that understand natural-language instructions. Texera is well suited for a wide range of applications, including “AI for Science,” by making advanced AI and data science capabilities accessible to a broader community. It can run on a laptop for local use or be deployed in the cloud to support scalable processing of large datasets.
Texera has been incubating since 2025-04-12.
### Three most important unfinished issues to address before graduating:
1. First incubating release (1.1.0-incubating): eight RCs cut in the window (rc2 through rc8); release vote / final still pending;
2. Increase community diversity, and need to identify and elect new committers from active contributors;
3. Trademark / brand assignment to ASF, need to confirm status with mentors.
### 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?
- 8 new first-time contributors in the last 3 months:
Anish Shivamurthy, Asish Kumar, Elliot Lin, Eugene Gu, Julie Cao,
Kyle Dang, Nicole Ying, Prateek Ganigi.
- 20 returning contributors.
- 1 new promoted committer: Meng wang (mengw15)
- dev@texera.apache.org list traffic: 262 messages, 17 unique posters across the window.
- Active participation in release votes from mentors（PJ Fanning and Ian Maxon) and community members.
### How has the project developed since the last report?
- In the past three months: 326 commits to main, 338 PRs merged
(400 opened), 286 issues closed (351 opened).
- We are actively preparing for the first apache release (1.1.0-incubating). A total of 8 RCs have been prepared and voted.
We had major updates:
- Fix many security issues reported by internal contributors and public users
- Create a new service named `Result Service` to give fine grained access to computing units instead of allowing computing unit talk to database directly
- Replace Ingress in our Kubernetes with Envoy Gateway which made our computing units distributed across distant machines without need to be part of one Kubernetes cluster
- Improve dataset upload experience by allowing resumable upload to support TB scale data upload with connection disruptions
- Improve our Github PR and issue management by adding automated tag and triage process
- Built first AI agent to help users create workflow without need to manually drag and drop operators and test
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
N/A
### When were the last committers or PPMC members elected?
April 6 2026, a new committer: Meng Wang (mwang15).
May 6 2026, a new committer: Xuan Gu (xuang7).
### Have your mentors been helpful and responsive?
We learned so much from our mentors, more specifically:
PJ: raised many PRs to address various security issues regarding version update, he also checked our first release and provide feedback very quickly in multiple rounds
Ian: we worked actively with him on our first release, he constantly provide feedback in our process based on his previous experience including how to manage the security issues and prioritize them
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [ ] (texera) Cezar Andrei
Comments:
- [ ] (texera) Gordon King
Comments:
- [ ] (texera) PJ Fanning
Comments:
- [ ] (texera) Ian Maxon
Comments:
### 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 has focused heavily on getting Release 0.6.0 through the incubator review process.
A significant portion of the recent mailing list discussions involved working through
review feedback to ensure the project is fully compliant with graduation requirements,
specifically around the proper attribution and packaging of legal files.
The community wants to finalize and publish Release 0.6.0 and then push for
graduation once the release process completes.
### How has the project developed since the last report?
The project progressed through Release 0.6.0 preparation, moving from RC3 up to RC5 votes.
The main technical work involved fixing the assembly process so the fat jar correctly
includes all licenses and notices from bundled dependencies. We also had some minor
repository maintenance, such as updating GitHub Actions for SBT setup.
The upcoming release officially brings support for Scala 2.13 and Spark 3.4.4.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [X] 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:
- [X] (toree) Luciano Resende
Comments: The podling should push graduation after release is out
- [ ] (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. Cutting the next release (0.4.0-incubating) — RC1 is being prepared this week to re-establish a regular release cadence.
2. Landing the in-flight Delta Kernel APIs implementation (PR #801) and pluggable table format support to unlock new format integrations.
3. Continued community growth - broadening the contributor base beyond the current core set and graduating new committers/PPMC members.
### 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?
- 4 unique contributors made commits during this commits during this period (Alex R, Kevin Liu, Nicolas Paris, Rishi Reddy Bokka).
- The community organizes a developer sync every 2 weeks and the last sync on 4th May we covered Delta Kernel, Hudi 1.x version upgrade, Paimon source completion, Parquet source completion and AI/MCP integration scope.[https://xtable.apache.org/community/sync/#typical-agenda]
- First scoping discussions started for AI-related work for XTable (initial agent skills and an XTable MCP server).
### How has the project developed since the last report?
- Parquet source matured significantly with expanded column stats support, schema conversion fixes, and
snapshot sync stability for partitioned multi-commit scenarios.
- Delta Kernel APIs implementation progressed and is pending merge (major milestone).
- Hudi conversion hardened with fixes for batch INSERT_OVERWRITE replace-commits and empty
earliest-commit-to-retain edge cases.
- Delta conversion improved with stricter checkpoint CRC enforcement and NPE fixes for binary fields in
nested schemas.
- Iceberg nested comment handling fixed for qualified names.
- Hudi version upgrade and pluggable table format support are in flight ahead of the next release.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [x] 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?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.
Our mentors have been helpful and responsive. Following last report's feedback to speed up the release cadence, an RC1 is being cut this week to demonstrate momentum
### 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:
- [ ] (xtable) Jesús Camacho Rodríguez
Comments:
- [ ] (xtable) Stamatis Zampetakis
Comments:
- [ ] (xtable) Jean-Baptiste Onofré
Comments:
### IPMC/Shepherd notes:
|