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

Incubator PMC report for November 2025

The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts.  As of October, there are 30 podlings under incubation. Five releases were made during the month, and no IP clearance was completed. No podlings retired during the month, and one person left the IPMC, as they have retired.

Mailing-list traffic in October covered the usual Incubator topics, including new proposals, release votes, and discussions on graduation readiness.

The Incubator wiki and Training Hub have been expanded to include additional materials. Some existing resources were converted into other formats (e.g., guides into slide decks and videos) to accommodate different learning preferences. Several new guides were created in response to minor recurring issues observed across podlings, including communication and third-party branding.

A consolidated guide, the Mentor Handbook, now serves as a single entry point that links to all materials, including guides, decks, short videos, and case studies, so mentors and podlings can find consistent references in one place.

Guides

• Podling Orientation Guide: Overview of entering incubation, including roles and expectations.
• Graduation & Beyond: Practical outline of what happens after graduation.
• Vendor Neutrality: Governance considerations for balanced decision-making, avoiding corporate dominance, and sustaining community independence.
• Mentor’s Tough Conversations Guide: Approaches for sensitive situations such as lack of engagement, governance misunderstandings, or interpersonal issues.
• Governance in Practice: Explains how consensus, merit, and "community over code" operate throughout incubation.
• How to Use the ASF Maturity Model: Guidance on applying the maturity framework for self-assessment.
• International / Cultural Awareness: Tips for cross-cultural communication and collaboration.
• Interacting with ASF Infrastructure: Practical information for working effectively with Infra processes and expectations.
• Communication in Apache Projects: Mailing list use, decision records, and public-by-default norms.
• Graduation Criteria: Explains how the IPMC assesses whether a podling is ready to graduate, outlining expectations for community maturity, diversity, and governance.
• Measuring Podling Health: Simple indicators for monitoring podling progress.
• Legal Basics: Key points about licensing, NOTICE and HEADER practices, and where to ask legal questions.
• Privacy and Data Handling: Guidance on managing contributor data, such as ICLAs, and maintaining privacy in podlings.

There is also new content based on the existing Incubator case studies. These are works in progress and include:

• IPMC Reflection and Oversight Guide: Case-based learning resource for recognising patterns in community health and effective oversight.
• Extended Incubator Case Studies: Case studies organised into community growth and diversity, corporate independence, complex incubation, lifecycle, and global collaboration.
• Release Vote Insights: Analysis of release-vote email traffic over ten years. This is being adapted by M&P into a blog post.

Additionally, based on the incubator case studies, several interactive scenarios have been developed.

All of this content is linked from the Training section of the Incubator site, which now includes a resources index grouping materials by topic and a lifecycle-based view that organises them along the incubation journey from onboarding to graduation. These resources directly support podling readiness and are already being used by several projects preparing for graduation.

A new Mentor Topic of the Month thread series has also been launched to encourage ongoing mentor engagement and knowledge sharing. The first discussion focused on how to grow new contributors. It's also a way to share some of the new training material. If this proves helpful, we'll continue it.

An experiment inviting podlings to take part in a structured six-month community health review is underway. The review helps projects reflect on progress, identify blockers, and discuss support needs with their mentors and the IPMC. Hamilton, PouchDB, and Texera were invited to participate. Hamilton is actively discussing this. The review offers an optional lightweight opportunity for projects to reflect on their progress, identify blockers, and discuss support needs with mentors and the IPMC.

There is a concern about HoraeDB; most of the original developers have departed, and the podling has been asked to outline a plan for attracting and developing new contributors. A minor website issue was noted with Gluten and GeaFlow. There was also a discussion regarding KIE hosting non-ASF releases and how this aligns with Incubator policy.

The usual discussions on release votes and incubation proposals continue, and we have accepted one new project, Caldera, into the Incubator. A vote to graduate Apache Wayang is underway.

Most podlings continue to make progress toward graduation, and the IPMC will continue to monitor long-running podlings. Both Livy and Toree are now actively discussing graduation, and several other projects are likely to graduate in the next couple of months. Pegasus was discussing graduation, but that has stalled as several core developers have left the project.

All podlings reported this month. Again, a couple of projects were contacted regarding issues in their reports and were pointed to the new reporting guide. Pegasus did not have mentor sign-off when the report was submitted.

Community

New IPMC members:

• none

People who left the IPMC:

• Jochen Wiedmann

New Podlings

• Caldera

Podlings that failed to report, expected next month

• None

Graduations

• DevLake

The board has motions for the following:

• Wayang

Releases

The following releases entered distribution during the month of September:

• Gluten 1.5.0
• Hamilton 1.89.0
• ResilientDB 1.10.0
• Polaris 1.2.0
• Seata-go 2.0.0

IP Clearance

• none

Legal / Trademarks

• N/A

Infrastructure

• N/A

Table of Contents

Burr
Cloudberry
Fesod s GeaFlow
GraphAr
Hamilton
HoraeDB
Pegasus
Pony Mail
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. Release
2. Build PPMC release muscle
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?

New issues from new users and new small time contributions added.

How has the project developed since the last report?

We're gearing up for the first release. Most of the PPMC is on Hamilton so we're taking those learnings and applying them here.

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:

N/A -- almost there!

When were the last committers or PPMC members elected?

May 2025

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:

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: 210 new emails on the Dev mailing list since the last report, covering community, technical and Apache-related discussions.
• GitHub Discussions: 14 new threads since last report.
• New Committers:
  • Sep 25, 2025 - Leonid Borchuk (leborchuk)
• Events:
  • Apache Cloudberry Meetup organized in Beijing on August 16, 2025, which attracted 30~ attendees. This meetup focused on the new features and highlights of the 2.0.0 release and the Apache way. See recap post at https://s.apache.org/xqyi9.
  • Our committer Leonid Borchuk presented a talk, "PAX — column store for Apache Cloudberry/Postgres 14", at PGConf.SPb 2025 in Saint Petersburg on September 29, 2025. See details at https://pgconf.ru/talk/2484244.

How has the project developed since the last report?

• Publish the first Apache Cloudberry (Incubating) 2.0.0 release on August 25, 2025. See announcement email at https://s.apache.org/fn13p
• PostgreSQL Kernel upgrade (14~>16): the work has been in progress. See the monthly report at https://s.apache.org/kp3lj
• 113 new commits to the main branch since the last report, focusing on CI, performance, bug fixes, and new features.
• Sub-repositories:
  • Archived the apache/cloudberry-devops-release repo and migrated these files to the devops/ directory of the main repository.
  • For the backup tool repos:
    • The cloudberry-gpbackup repo has been renamed to cloudberry-backup, reflecting the project’s independence and alignment with the Cloudberry brand. Its codebase has synced with the GP’s archived version.
    • The core files from apache/cloudberry-gpbackup-s3-plugin have been merged into the cloudberry-backup repos under plugins/s3plugin. Now, the S3 plugin will be installed together with Cloudberry Backup.
  • The cloudberry-pxf is still in progress on the archived Greenplum commits sync to Cloudberry.
  • cloudberry-go-libs has synced with the GP’s archived version.
• Started the discussion on the next release 2.1.0. See discussion at https://s.apache.org/rx7s8
• It has been one year since Cloudberry joined the ASF Incubator. Here is our Roadmap recap at https://s.apache.org/5fxn9
• Ecosystem:
  • The community developers are working with the Apache MADlib team to add support for Cloudberry to MADlib upstream. See the PR at https://github.com/apache/madlib/pull/627
  • The PostGIS for Cloudberry has been upgraded from 2.5 to 3.3.2

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?

• Sep 25, 2025 - Leonid Borchuk (leborchuk)

Have your mentors been helpful and responsive?

Yes. Appreciated their help and support on the release process.

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: Pleased to see cooperations between cloudberry and madlib

IPMC/Shepherd notes:

[PJF] The community seems healthy. Maybe it's time to move towards graduation.

---

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. Publish the first release under the Apache Incubator.
3. Continue to grow the community and word towards the ASF maturity Model.

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 update project's website, now you can see details in Apache Analytics.
2. We have 5 new contributors.

How has the project developed since the last report?

The community is actively working on the first release under the Apache Incubator, which is currently planned for December.

1. Developement of new features is in progressing.
2. The project executed the Fuzz chaos test and fix bugs at the suggestion of the mentor.

How would you assess the podling's maturity?

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

Date of last release:

N/A

When were the last committers or PPMC members elected?

N/A

Have your mentors been helpful and responsive?

Yes.They are very nice and actively.

1. Dave Fisher pointed some wrong process about the election of committer(fixed).
2. PJ Fanning give suggestions about project-module and jdk-version.
3. Huajie Wang help community on how to design logo.
4. tison tells many of the small but important copyright details.

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

Yes, everything is fine.

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.

Three most important unfinished issues to address before graduating:

1. Enhance the diversity of the community (attracting more committers, contributors, and users).  
2. Release more versions under 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?  

1. Four new contributors have joined the community.
2. Participated in 2025 CSDI Summit in Shenzhen, China, and presented work in the field of AI.
3. Participated in the open source initiative OSPP 2025 and helped new contributors resolve specific project issues.

How has the project developed since the last report?

1. Five new features have been merged, including support for the distributed Paimon graph store, a new algorithm implementation for the incremental minimum spanning tree, JDK 11 compatibility and more. Several bug fixes and other improvements have also been made.
2. The Apache GeaFlow website is published with both Chinese and English support.
3. The first community release is in the second round of voting (v0.7.0-rc2)

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:

N/A

When were the last committers or PPMC members elected?  

None since entering the incubator. We have several active community members and PPMC will review recent contributors and consider the committer nominations.

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. Growing the community(attracting more committers, contributors and users)
2. Release more ASF-compliant versions

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. Released a new version V0.13.0
2. 5 new contributors completed PR merge

How has the project developed since the last report?

1. Merged 27 PRs since the last report
2. The java-info module changed user-facing API
3. Improve the ci test and coverage 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:

2025-08-29

When were the last committers or PPMC members elected?

2025-07-14

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. Release other packages under apache process.
2. Train more of PPMC to run a release.
3. Have more releases.

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?

Several new contributors to the repo.

How has the project developed since the last report?

We published our first main package under apache!

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

When were the last committers or PPMC members elected?

April 2025

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.

We're not a java project, so things aren't as straightforward to release -- which most of the documentation is geared towards.

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

Yes -- no 3rd parties with issues.

Signed-off-by:

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

1. Release more version
2. Grow community(attract more users/committers)
3. Finish the new metrics engine

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

Several core developers have left the project, causing a slowdown in development this year. We expect development to get back on track next year.

How has the community developed since the last report?

Attend the OSPP 2025 with one project.

How has the project developed since the last report?

An in-house prometheus remote write format parser has been merged.

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:  

2024-12-10

When were the last committers or PPMC members elected?  

Neo Chen, at 2024-12-25

Have your mentors been helpful and responsive?

Yes, they are helpful when release version and other trivial things.

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

Yes, we're doing well with this.

Signed-off-by:

•  (horaedb) tison
  Comments:
•  (horaedb) Shaofeng Shi
  Comments:
•  (horaedb) Gang Li
  Comments:
•  (horaedb) Von Gosling
  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. The graduation discussion has been initiated, but not enough PPMC members have participated yet; therefore, the discussion is currently blocked.

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

Many core members of the project have left, leading to a decline in community activity and consequently blocking the graduation discussion.

However, there are still some PPMC members and contributors maintaining the project.

The reason there has been no release for nearly two years since December 2023 is that several major features were planned for Pegasus 2.6.0, such as FQDN support and a refactored metrics framework. However, due to the inactivity of many core members, progress on these major features has been difficult. At present, the remaining active members are doing their best to move things forward.

How has the community developed since the last report?

Some new contributors have joined the project development.

How has the project developed since the last report?

Introduce some new features, enhancements and fixes, including:

• support encrypted password file during SASL authentication for ZooKeeper C client
• the underlying network communication and the write path have been optimized
• some bugs of replica server, scripts, java and go client have been fixed
• some dependencies of java client have been upgraded to the secure versions

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?

Yes.

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:

---

PonyMail

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. Make a release of Pony Mail Foal
2. Decide on the future direction of the project. PMC or retirement.

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

Nothing at this time.

How has the community developed since the last report?

The community is slowly discussing their exit strategy.

How has the project developed since the last report?

Responding to some concerns

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:

2019-04-05 Pony Mail 0.11

When were the last committers or PPMC members elected?

2021-04-02 Sean B Palmer

Have your mentors been helpful and responsive?

See above.

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

If not what actions has the PPMC taken to correct this?

Has the VP, Brand approved the project name? Yes

Signed-off-by:

•  (ponymail) John D. Ament
  Comments:
•  (ponymail) Dave Fisher
  Comments: Doing my best slowly move the podling one way or another.

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 the ASF. Currently awaiting feedback from ASF trademark counsel.

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. 26 new code contributors have joined the community (622 contributors in total)
2. 3 new committers were elected, and 1 PPMC members were elected.
3. In the open-source programming events, OSPP and GSoC, through the joint efforts of multiple mentors and students, we completed the finalization of 5 projects, including 3 AI-related ones.

How has the project developed since the last report?

1. Since the last report, we've merged 145 PRs, which include over 10 new features.
2. Since the last report, we have released one official versions: seata-go 2.0.0.
3. Since the last report, we have fixed more than 25 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?

2025-10-16

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: Project community keeps active. The PMC is finishing the preparation for the graduation.
•  (seata) Justin Mclean
  Comments:
•  (seata) Huxing Zhang
  Comments: The project is in good shape towards graduation.
•  (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. The Apache website (texera.apache.org) is still ongoing
2. We still have one library (rpy2) that is not Apache friendly

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?

We had three new external contributors and also an external contributor who helped us to identify the security issue.

How has the project developed since the last report?

The followings are some of the important updates on project development:

• Reorganize the code base: previously, the naming convention was edu.uci.ics and its now changed to org.apache.texera to be compliance with Apache
• Add ML training operators for linear and logistic regression
• Add a new micro-service named access control service which secures socket connection between computing unit and user

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:

NA

When were the last committers or PPMC members elected?

July 4 2025

Have your mentors been helpful and responsive?

Yes, PJ and Ian helped us in many ways including:

• PJ raised many PRs including replace Akka actor since its license is not Apache friendly
• Ian gave us insight on how to improve our security

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: Getting web site up and running would be useful.
•  (texera) Ian Maxon
  Comments: Looking forward to the first incubating release, great to see the package name change.

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?

Release 0.6 has been voted by PPMC and is being reviewed in incubator general mailing list. 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

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?

• Cheng Pan was added to the PPMC on 2023-08-28

Have your mentors been helpful and responsive?

None

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

No trademark issues

Signed-off-by:

•  (toree) Luciano Resende
  Comments: The podling should push graduation after release is out process
•  (toree) Ryan Blue
  Comments: Good to see a discussion about graduation in the community. You may want to update the "unfinished issues" section and remove #1.
•  (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, Syncing to New 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. An XTable contributor presented an integration talk with one of Apache Polaris PMC during Community Over Code 2025
2. Two new first time contributors have merged their first PR's.
3. More users are trying to use XTable in production environments and the community has been helping them succeed.
4. We have added two new members to the PPMC.

How has the project developed since the last report?  

1. The implementation for the XTable REST Service was introduced in the release 0.3.0.
2. The implementation for adding a conversion source for Apache Parquet files was recently landed.
3. Community is working on adding support for Delta Lakes Kernel APIs for handling conversion.
4. Community is currently working on supporting an Apache Paimon Conversion Source.

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

When were the last committers or PPMC members elected?

2025-11-04

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: It's nice to see that the community is growing. Looking forward seeing more involved in the oversight of the project.
•  (xtable) Jean-Baptiste Onofré
  Comments: Good progress in the podling. The community is active and I agree that building the community is the main action item right now.

IPMC/Shepherd notes: