FINAL 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 August 05 Podling reports due by end of day
Sun August 09Shepherd reviews due by end of day
Sun August 09Summary due by end of day
Tue August 11Mentor signoff due by end of day
Wed August 12

Report submitted to Board

Wed August 19Board meeting


Shepherd Assignments

Calvin KirsBurr
Calvin KirsTexera
Dave Fisher Cloudberry
Drew FarrisSeata
Drew FarrisToree
Justin McleanGraphAr
P. Taylor GoetzXTable
PJ FanningAmoro
PJ FanningCasbin
Timothy ChenGeaFlow
Willem JiangFesod
Willem JiangPegasus
XuanwoHamilton

Incubator PMC report for August 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 24 podlings under incubation. In July, the Incubator made six releases, and a release vote for one podling is currently underway. There were no additions or removals to IPMC membership.

Two podlings graduated in July: Apache Fluss and Apache Pony Mail, after incubating since 2016. A vote to graduate Apache ResilientDB is currently underway following an extended discussion on the general list.

Mailing list discussion otherwise focused on release voting, the ResilientDB graduation, and an experimental AI concierge skill for answering Incubator questions.

Casbin's first release candidate passed its dev list vote and came before the IPMC, where it received a binding -1 due to signing, checksum, and license header issues; the vote was canceled, and a second candidate is being prepared. The podling has stopped publishing snapshot CI builds in favor of properly voted releases. The IP clearance questions raised last month have been resolved.

OpenServerless has still not made an ASF release despite over two years of incubation, although development activity remains high. Encouragingly, the community began discussing its first source release on its dev list in late July, with mentors providing guidance on the ASF release process. The IPMC hopes to see a release candidate and vote follow.

Pegasus, incubating since 2020, has had no release in over 12 months and its activity has dropped to near zero, with no dev list traffic in July and a single active committer in the past quarter. The IPMC will follow up with the podling and its mentors.

PouchDB has now passed 12 months of incubation without an ASF release. Commit activity continues, but its dev list was silent in July, and it has yet to correct the redirection of the legacy pouchdb.com site.

XTable, which had gone over 12 months without a release, attempted one in July. The vote on a 0.4.0-incubating release candidate was canceled due to a source build failure and license documentation issues; a second candidate is expected once these are resolved.

Toree continues to show very low activity, with no dev list traffic in July, two commits over the past quarter, and no visible progress on the release candidate prepared in May.

GeaFlow made its 0.8.0-incubating release in late June, but overall activity has contracted sharply over the past quarter, with development now down to one or two active committers and little dev list discussion; this will be watched.

The IPMC continues to monitor long-running podlings and will follow up on any community concerns as needed.

When submitted 3 podlings (cloudberry, graphar, pegasus) did not have mentor sign-off; they been notified and will hopefully sign off before the board meeting

Community

New IPMC members:

  • none

People who left the IPMC:

  • none

New Podlings

  • none

Podlings that failed to report, expected next month

  • None

Graduations

  • Fluss
  • Pony Mail

  The board has motions for the following:

  • None

Releases

The following releases entered distribution during the month of July:

  • Auron 8.0.0-incubating
  • GeaFlow 0.8.0-incubating
  • Hamilton (contrib) 0.0.9-incubating
  • Hamilton (lsp) 0.2.0-incubating
  • Hamilton (sdk) 0.9.0-incubating
  • Hamilton (ui) 0.0.18-incubating

IP Clearance

  • none

Legal / Trademarks

  • N/A

Infrastructure

  • N/A

Table of Contents

Amoro
Burr
Casbin
Cloudberry
Fesod
GeaFlow
GraphAr
Hamilton
Pegasus
Seata
Texera
Toree
XTable

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:

  1. Fix possible and potential security vulnerability issues.
  2. Release more versions under ASF.
  3. 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 3 new contributors
  • Jinsong and ZhuoJun presented technical practices related to Apache Amoro at Community Over Code Asia 2026.

How has the project developed since the last report?

  • Merged 40+ PRs.
  • Releasing 0.9.0-incubating, the release vote is currently underway on the dev mailing list.

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

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?

No Answer

Signed-off-by:

  •  (amoro) Justin Mclean
    Comments:
  •  (amoro) Zhongyi Tan
    Comments:
  •  (amoro) Yu Li
    Comments:
  •  (amoro) Xinyu Zhou
    Comments:
  •  (amoro) Kent Yao
    Comments:

IPMC/Shepherd notes:

[PJF] there are a number of issues on the private mailing list that have not been addressed even after multiple months.

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 knowledge & ability through PPMC.
  2. Build community
  3. Build roadmap

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?

Was on the front page of hackernews - drove some discord joins.

How has the project developed since the last report?

Added new PPMC member.

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-05-09

When were the last committers or PPMC members elected?

2026-05-22

Have your mentors been helpful and responsive?

N/A

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

N/A

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:

  1. Community Growth
  2. Grow the PPMC

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?

Petitioned for an additional PPMC member; in process of vetting and voting on them. Github Stars are over 7.2k.

How has the project developed since the last report?

We had 4 new PRs merged and closed on GitHub. Added .asf.yml and NOTICE files to repo. Updated README file. Updated submodule pin references for plugins. We handled 3 software library version updates.

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:

No Apache release yet.

When were the last committers or PPMC members elected?

At founding/incubation.

Have your mentors been helpful and responsive?

Yes.

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

Finalizing third-party references and branding references, including documentation and website references as well as plugin repository mentions and references.

Signed-off-by:

  •  (caldera) Kevin Ratnasekera
    Comments:
  •  (caldera) Francis Chuang
    Comments: Steady progress is being made.
  •  (caldera) PJ Fanning
    Comments:
  •  (caldera) Gordon King
    Comments:

IPMC/Shepherd notes:

Casbin

Casbin is a powerful, efficient open-source access control framework that provides a unified, model-driven approach to authorization. Built on the PERM (Policy, Effect, Request, Matchers) metamodel and its domain-specific language, Casbin brings ACL, RBAC, and ABAC together under one model so that policies can be expressed flexibly and enforced at a fine-grained level. It offers high-performance enforcement and a broad multi-language ecosystem spanning Go, Java, Node.js, Python, .NET, C++, and Rust.

Casbin has been incubating since 2026-02-07.

Three most important unfinished issues to address before graduating:

  1. Complete the first official Apache incubating release.
  2. Clarify repository scope, release plans, and IP/grant coverage for the large set of Casbin repositories under the Apache GitHub organization.
  3. Continue building a diverse, public, mailing-list-centered community and keep project decisions visible on dev@casbin.apache.org.

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

No new issues require special attention from the IPMC or ASF Board at this time. The podling is addressing the release-compliance findings from RC1 and is preparing RC2. The review of repository scope and IP/grant coverage remains ongoing with mentor and IPMC guidance.

How has the community developed since the last report?

  • dev@ had 8 messages across 4 threads, with 4 participants.
  • The public dev list continued to carry Incubator report review and discussion about repository scope and IP/grant coverage.
  • Participation remained concentrated among existing contributors. Broadening the active contributor and discussion base remains a community priority.
  • The main apache/casbin repository reached about 20.3k GitHub stars.

How has the project developed since the last report?

  • Across 239 tracked Casbin Apache GitHub repositories, 6 PRs were merged and 0 issues were closed from 2026-07-01 to 2026-07-31. All six merged PRs were in the Go core repository, apache/casbin.
  • The merged work focused on NOTICE and DISCLAIMER corrections, migration to standard ASF license headers, accounting for a bundled MIT-licensed configuration file, and adding a project-specific Apache RAT policy.
  • The resulting source-archive policy was validated with Apache RAT 0.18 at zero unapproved or unknown files, and tests passed both in the repository and from a clean source archive.
  • RC1 was cancelled after the binding IPMC review. The release remains in RC2 preparation, and no new release vote had opened by the end of July.

How would you assess the podling's maturity?

The podling is actively learning and applying the ASF release process. The first IPMC release review exposed compliance gaps that are being addressed, while community participation remains concentrated and needs to broaden. The podling is not yet nearing graduation.

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

Date of last release:

No official Apache release yet.

When were the last committers or PPMC members elected?

2026-02-07

Have your mentors been helpful and responsive?

Yes. Mentors and IPMC members have provided detailed, actionable feedback on release compliance, repository scope, and IP/grant coverage.

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

The project name has been approved in PODLINGNAMESEARCH-251. The PPMC is continuing to review release, website, and repository materials for Apache branding and trademark requirements.

Signed-off-by:

  •  (casbin) Hao Ding
    Comments:
  •  (casbin) Huajie Wang
    Comments:
  •  (casbin) Hulk Lin
    Comments:
  •  (casbin) Jerry Shao
    Comments:
  •  (casbin) Zili Chen
    Comments:

IPMC/Shepherd notes:

[PJF] There are a number of open issues on the private mailing list where the issues have been open for many months.

Cloudberry

 Apache Cloudberry is an advanced and mature open-source Massively Parallel Processing (MPP) database, derived from the last open-source version of the Greenplum Database® but built on a more modern PostgreSQL kernel and with more advanced enterprise capabilities. Cloudberry can serve as a data warehouse and can also be used for 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 issues.

How has the community developed since the last report?

  • The community continued its public bi-weekly meetings, holding six meetings from May through July 2026. Discussions covered the PostgreSQL 16 kernel upgrade, release coordination, CI and packaging, ecosystem projects, documentation, community governance, and open technical topics.
  • New Committers: Anton Kurochkin (@woblerr) and Liu Shengsong (@lss602726449) were announced as new committers on June 26 and July 6, respectively.
  • Contributors and community participation continued to grow through work on the main repository and related ecosystem projects. The community also discussed new Kubernetes operators and the creation of an Apache Cloudberry Command Center repository.
  • Community governance and responsible AI use continued to receive attention. The community discussed the AI guideline and the use of AI-assisted code review tools, with AI-assisted code review tools, such as GitHub Copilot, were discussed as optional review suggestions subject to normal community review.
  • Events and outreach:

How has the project developed since the last report?

  • PostgreSQL kernel upgrade and core development:
    • Merged the PostgreSQL 16 kernel upgrade into the main branch with 5730 commits. The remaining FIXME items are planned to be addressed as part of the future 3.0 release.
    • Started discussion about a future kernel upgrade from PostgreSQL 16 to PostgreSQL 18.
    • Continued PostgreSQL 14.x maintenance on the 2.x stable branch, including work to backport 14.8 and archive-related fixes.
    • Added security fixes for several CVEs and continued dependency and security maintenance across the repositories.
    • New extensions:
      • Added the gp_relsizes_stats extension.
      • Introduced the yezzey extension for the 2.x stable branch as a submodule.
      • Added the TRY_CONVERT extension.
      • Added the reject_partition_fullscan extension.
    • Continued ORCA and planner improvements, including fixes for CTE handling, intra-segment parallel table scans, HAVING and grouping-set handling, non-ASCII column aliases, empty-partition statistics, outer-join predicate pushdown, and other correctness and stability issues.
  • datalake_fdw: Started implementing Iceberg support in the datalake_fdw.
  • Ecosystem and sub-repositories:
    • cloudberry-pxf:
      • Continued the 2.2 release plan.
      • Added Java 21 support, upgraded the Gradle wrapper, updated HBase and Log4j dependencies, improved S3-related Testcontainers coverage, and added session and command-count information to logging context.
      • Applied security and dependency updates and restored green CI testing.
    • cloudberry-backup:
      • Completed the Go 1.25 upgrade and continued PostgreSQL 16 support work.
      • Pinned the CI branch to Cloudberry 2.x stable branch and applied dependency updates to address security alerts.
      • Added the gpbackup_exporter Prometheus exporter for the backup history database.
    • cloudberry-go-libs:
      • Added a new CI/CD workflow and completed the ASF compliance work. The project is ready for the 2.2 release.
    • Other ecosystem work:
      • WAL-G added support for PAX incremental backups.
      • Odyssey 1.5.1 was released, and Odyssey support was documented on the Cloudberry website.
      • Community members developed Kubernetes operators for Cloudberry.
      • Yandex Cloud plans to donate the Command Center project to Apache Cloudberry - https://s.apache.org/urvsc
  • Release, CI, and packaging:
    • Release:
      • Provided the convenience packages for 2.1 release.
      • Started preparing Apache Cloudberry (Incubating) 2.2.0. By the end of July, the release was considered ready to enter the release process, with remaining work including cherry-picking changes to REL_2_STABLE, and finalizing PXF Rocky Linux 10 support.
      • Created the release runbook wiki page for the release manager.
    • CI workflows:
      • Added Rocky Linux 10 workflow support.
      • Completed the CI consolidation work from OS-specific CI workflows into matrix-based workflows for easier maintenance and future platform expansion.
      • Bumped the Go version to 1.25 in the development Docker images and CI workflows.
      • Planned to add a macOS CI workflow.
    • Packaging:
      • Improved RPM packaging for the core repository, including custom installation prefixes and support for installing multiple major versions side by side.
      • Merged the source-release-based convenience packages workflow for the main repository, cloudberry-backup and cloudberry-pxf for the coming 2.2+ releases.
  • Website and documentation:
    • Upgraded the website to Docusaurus 3.10.2 and continued UI improvements.
    • Added the “Powered by” page and integrated cloudberry-pxf documentation into the main website.
    • Added a project history page and ecosystem documentation for Odyssey and WAL-G.
    • Added a new page on backward-incompatible changes from Greenplum 6.x.
    • Refreshed the deployment guide.
    • Published five new blog posts to share the latest community news.

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:

  • April 14, 2026 - Apache Cloudberry (Incubating) 2.1.0

When were the last committers or PPMC members elected?

  • June 22, 2026 - Anton Kurochkin (woblerr) was announced as a new committer.
  • July 6, 2026 - Liu Shengsong (@lss602726449) was announced as a new committer.

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?

No.

How has the community developed since the last report?

  1. We have voted and approved two new committers.
  2. There five new contributors joined project and contribute some good features.
  3. Shuxin Pan will represent Fesod in one accepted session at Community Over code Asia 2026.
  4. We actively communicate with relevant security reporters, striving to ensure the reliable and security.

How has the project developed since the last report?

  1. We released a fix version (2.0.2-incubating) in May to address CVE-2026-49328.
  2. Overall project development is proceeding smoothly, with no obstacles hindering our progress.
  3. We are currently finalizing details for the second official release, scheduled for mid-August.
  4. Regarding the vulnerability, we have confirmed the remediation details with the reporter and the ASF security team via the private mailing list.

How would you assess the podling's maturity?

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

Date of last release:

2026-05-28

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' helpful suggestions.

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

Not aware of any issues.

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 large-scale graph storage, hybrid graph and table processing, real-time and offline graph computing, and interactive graph analysis. The community is also developing Graph Memory as infrastructure for agent memory.

GeaFlow has been incubating since 2025-06-06.

Three most important unfinished issues to address before graduating:

  1. Broaden the contributor and committer base across organizations and regions.

  2. Keep review and triage timely as first-time contributions increase.

  3. Maintain a predictable release cycle and high project stability.

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?

Since May, the community has focused on making the path into the project clearer without lowering review standards. It published 13 good first issues with context, reference code, test guidance, and explicit acceptance criteria. These issues have attracted contributions from both first-time and returning contributors. Maintainers are holding concentrated review rounds, giving specific feedback, and resolving overlapping implementations in public based on correctness and maintainability.

In July, the PPMC initiated a committer nomination and vote for Xinyuan Chen (GitHub: kitalkuyo-gita), based on sustained contributions to graph algorithms, ISO-GQL, design discussions, and reviews of other contributors. Xinyuan was also recognized as a 2025 Apache Doris Community MVP.

The community is participating in Open Source Promotion Plan 2026, GitLink Programming Summer Camp, and the Open Source Academy program. Mentored projects cover GraphRAG, hybrid graph-text-vector retrieval, and graph-native memory. Students use the normal issue, discussion, review, and test process, with the goal of continuing as community contributors after the programs end.

Litao Lin, Xinyuan Chen and Yao Zhongqiang will represent GeaFlow in three accepted sessions at Community Over Code Asia 2026. The sessions are in the Data + AI, Streaming, and Incubator tracks and cover agent memory, streaming memory, and GeaFlow's incubation and technical practice.

How has the project developed since the last report?

The 0.8.0-incubating source release entered distribution on June 10 and was announced on July 3. It is the second community release since GeaFlow entered the Apache Incubator.

The release added vector storage and retrieval, Graph Memory and AI components, graph algorithms, more ISO-GQL predicates, and new or improved connectors. It also improved JDK 8 and JDK 11 build profiles and release tooling. The release removed bundled Category-X MySQL JDBC artifacts and other non-source content from the source distribution.

Merged PRs added math and date functions, a Doris connector, graph algorithm regression tests, and safer cluster exception tests. Open work includes MongoDB, ClickHouse, and Redis connectors, a SQLite store, graph algorithms, SQL functions, ISO-GQL support, and an incremental resident keyword index for AI search.

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-07-03

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?

No known issues.

Signed-off-by:

  •  (geaflow) Willem Ning Jiang
    Comments:
  •  (geaflow) Xin Wang
    Comments:
  •  (geaflow) Jingsong Lee
    Comments:
  •  (geaflow) Paul King
    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. 3.Cultivate more committers and release managers

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. Several new contributors completed PR merges.

  2. A native Go SDK effort started and is attracting new contributors.

How has the project developed since the last report?

1.Merged 21 PRs since the last report.

  1. C++ library: new features and bug fixes for builders, and upgraded to Apache Arrow 24.0.0.

  2. Rust module: completed the builder layer of the Rust roadmap.

  3. Bootstrapped a native Go SDK, with more language support in progress.

  4. CI/CD improvements: fixed build issues across C++, Python and Rust workflows, and added PR template checklist.

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?

2026-04-22

Have your mentors been helpful and responsive?

The mentors are very helpful and responsive.

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

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. Get more PPMC comfortable with releases.
  2. Add to PPMC
  3. Build community

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?

Still people joining slack.

How has the project developed since the last report?

More first time contributors.

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-07-13

When were the last committers or PPMC members elected?

N/A

Have your mentors been helpful and responsive?

No answer

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

No answer

Signed-off-by:

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

  1. 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?

None.

How has the community developed since the last report?

Overall community activity remained limited during this reporting period, and no new committers or PPMC members were added.

The community will continue encouraging active contributors to take greater responsibility for development, code review, and release work.

How has the project developed since the last report?

Project development remained relatively limited during this reporting period. A small number of changes were merged, including improvements to the new metrics framework and updates to GitHub Actions to comply with ASF infrastructure requirements. Several additional bug fixes and improvements have been proposed and are currently under review.

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:

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 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. 2 new committers were elected.
  2. We have prepared 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 78 PRs, primarily including several new architectural evolution features.
  2. Since the last report, we have introduced AI Skills exploration into our roadmap.

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-12

When were the last committers or PPMC members elected?

2026-07-24

Have your mentors been helpful and responsive?

Our mentors have been very helpful and responsive.

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

No Trademark issues.

Signed-off-by:

  •  (seata) Sheng Wu
    Comments:
  •  (seata) Justin Mclean
    Comments:
  •  (seata) Huxing Zhang
    Comments: The podling is still handling trademark issues with ASF, 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. Publish a sequence of ASF releases following the scheduled quarterly release cadence.

  2. Increase community diversity, and identify and elect new committers and PPMC members from active contributors.

  3. Grow real-world adoption and the user community of the project.

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?

  • dev:
  • 21 new first-time contributors made their first commit between May 2026 and July 2026; 44 contributors were active in total.
  • The dev@ mailing list had 181 direct messages from 26 unique posters, including release votes, design RFCs, and policy votes.
  • Design and feature discussions increasingly happen on GitHub Discussions, with 61 new threads between May and July 2026.
  • Three universities (UCI, UCLA, and UMich) received an NSF award of nearly $9M to develop a national center to use the Texera project to provide services to research labs and communities for three years (2026 - 2029).
  • Three monthly community sync meetings were held (June 2, June 30, and July 28); the meeting minutes are published at https://texera.apache.org/monthly-meetings
  • users:
  • Apache Texera (Incubating) was presented at the American Diabetes Association conference in New Orleans, introducing the project to the diabetes research community.
  • The team launched dknet-ai.org and ran the dkNet-AI Texera Agent Hackathon.
  • Texera was used by about 20 students in a summer camp organized by dkNET.
  • Texera was used by 12 high-school students to learn data science and AI in the DS4ALL summer program (https://ds4all.ics.uci.edu/summer2026).

How has the project developed since the last report?

How would you assess the podling's maturity?

  •  Initial setup
  •  Working towards first release
  •  Community building
  •  Nearing graduation
    •  Status file tasks signed off
    •  Suitable name — checked 2025-04-12
    •  Ability to create Apache releases — demonstrated with 1.1.0-incubating; 1.2.0 in flight
    •  Community readiness
  •  Other:

Date of last release:

2026-05-20, Release v1.1.0-incubating

When were the last committers or PPMC members elected?

May 6, 2026, a new committer: Xuan Gu (ASF id: xuangu).

Have your mentors been helpful and responsive?

Yes, the mentors have been very helpful and responsive. In particular, Ian Maxon provided extensive help during the v1.2.0-incubating release reviews and joins the monthly sync meetings.

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 slowed down this last couple months and there hasn't been much progress on getting Release 0.6.0 through the incubator review process.

The original community plan was 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?

There has been little progress with Release 0.6.0 preparation for RC6 vote.

The upcoming release officially brings support for Scala 2.13 and Spark 3.4.4 which is already getting a little old.

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
  •  (toree) Ryan Blue
    Comments:
  •  (toree) Weiwei Yang
    Comments:

IPMC/Shepherd notes:

XTable

XTable is a cross-format converter for lakehouse tables. It translates the metadata that describes a table - schema, partitioning, file listings, column statistics and snapshot history between Apache Hudi, Apache Iceberg, Delta Lake, Apache Parquet and Apache Paimon without rewriting or copying the underlying data files. A single physical copy of a dataset can therefore be read by engines and catalogs across various platforms.

XTable has been incubating since 2024-02-11.

Three most important unfinished issues to address before graduating:

  1. Shipping 0.4.0-incubating. rc1 was voted on 2026-07-22 and cancelled on 2026-07-27 over a source release build failure and LICENSE/NOTICE gaps in bundled jars; fixes are merged or in review and rc2 is next.
  2. Grow the contributor base and elect new committers/PPMC members from it. Patches now arrive from a reasonably wide set of people, but review and merge activity is still concentrated in a few hands. Publishing committer/PPMC expectations (done this period) was the first step; converting active contributors into committers is the next.
  3. Distribute release and maintainer responsibility beyond one individual. One person has acted as release manager for the last four releases. A [DISCUSS] Rotating release managers thread is open on dev@, and a PPMC member has already volunteered to take a future release.

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 unique contributors had pull requests merged during this period, with open pull requests under review from 5 new contributors.
  • 14 new issues opened by 6 distinct reporters, 11 closed.
  • Committer and PPMC expectations are now published on the website, prompted by two dev@ threads including one from a contributor asking about the path to committership.
  • GitHub Discussions are now mirrored to dev@, so design conversation is archived on the mailing list.
  • New dev@ threads covered indexing across table formats, xtable-spark-runtime, a Spark-free Java runtime, rotating release managers and issues/bugs reported by community users running XTable in various platforms.
  • The developer sync continues every 2 weeks. [https://xtable.apache.org/community/sync/#typical-agenda].

How has the project developed since the last report?

  • 26 pull requests merged across 7 contributors and 2 of them are first-time contributors since May 2026.
  • Delta Kernel conversion target merged (#801), removing the Spark dependency for Delta targets - the major in-flight milestone from the last report.
  • Hudi 1.x upgrade merged (#772) with table version 9 support and tests parameterized across versions 6 and 9 (#834, #835).
  • New xtable-spark-runtime module (#843): a thin drop-in bundle for Spark 3.4 and 3.5, validated in CI against a real Spark distribution, so metadata translation can run inside existing Spark pipelines.
  • Parquet source matured further with incremental sync (#768).
  • Release engineering hardened from 0.4.0-incubating rc1 validation feedback.
  • Website: required ASF navigation links added (#856), Docusaurus upgraded (#863), CSP violations fixed (#764, #877).
  • main moved to 0.5.0-SNAPSHOT and branch-0.4 was cut for the 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:

The community is targeting a monthly release cadence once 0.4.0-incubating ships, and nearing graduation in the next six months. More features are planned as part 0.5.0, 0.6.0 etc., along with blog posts and meetup talks, including from companies running XTable in production.

Date of last release:

2025-06-04 (0.3.0-incubating). rc1 for 0.4.0-incubating was cancelled on 2026-07-27; rc2 is in preparation

When were the last committers or PPMC members elected?

2025-11-09. A further PPMC vote was held on private@ this period; the feedback was to wait for more concrete individual contributions, so no new member was elected

Have your mentors been helpful and responsive?

Our mentors have been helpful and responsive. They have opened the threads on rotating release managers and on documenting committer/PPMC expectations.

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

Yes. The required ASF navigation links flagged by the Clutch report were added to the website this period.

Signed-off-by:

  •  (xtable) Jesús Camacho Rodríguez
    Comments:
  •  (xtable) Stamatis Zampetakis
    Comments:
  •  (xtable) Jean-Baptiste Onofré
    Comments: I'm waiting the report to review and sign. As I'm on vacation, it's possible I will miss the sign off.

IPMC/Shepherd notes:

  • No labels