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

Three podlings entered incubation in August: Apache Maka, Apache Asyncband and Apache NullAway. Graduation votes passed for Apache ResilientDB and Apache Iggy, and Iggy has graduated. JB was on holiday, so the board will see ResilientDB this month. Auron also discussed graduation.

Mailing list discussion otherwise focused on new podling proposals, release voting, and the status of several long-running podlings. Related discussions covered metrics and guidelines for adding committers, and handling of multiple podling status files.

Casbin's second release candidate passed, making the podling's first ASF release.

Texera raised a question on the general list about the sites it is running alongside its ASF website, which mentors are following up.

Pegasus has been in incubation since June 2020 with no release since December 2023. The IPMC is discussing whether it should be retired. Neither the podling nor its mentors have responded so far.

Toree, which has been incubating since December 2015, was the subject of a similar status discussion. The March release vote was never completed; the replacement candidate discussed in May has not appeared. A PPMC member has since said the podling should be retired; the mentors have not responded.

OpenServerless has still not made an ASF release after more than two years of incubation. Development activity remains high, but the first source release discussed in late July has not happened. The podling acknowledges that much coordination still happens on WhatsApp and in private meetings rather than on the dev list.

PouchDB has now been incubating for 16 months without an ASF release. Its dev list has been silent for two consecutive months. The legacy pouchdb.com site now redirects to pouchdb.apache.org. The podling reports that discussion is happening on Slack and in triage meetings rather than on the dev list.

XTable released 0.4.0-incubating in August, its first release since June 2025, and is planning future releases.

OzHera is handling its first security vulnerability report with mentor guidance.

Five proposals were under discussion during August: Aegis MCP Governance Gateway, NullAway, OpenCrawling, MEA and Quilzo.

The IPMC discussed adding AI-related questions to the podling proposal template, following the code provenance issues raised during the Maka discussion.

Two sets of AI tooling have been added to the incubator repo and are open for review: a set of skills covering common IPMC tasks such as report review, release vote checking, graduation packets, and branding sweeps, and the first three AI tutor lessons for Incubator training with a roadmap of twenty-six lessons across eight tracks. Both were drafted with AI assistance and human-reviewed against the policy pages.

Community

New IPMC members:

• Chojan Shang
• Raúl Cumplido
• Xinyu Tan

People who left the IPMC:

• None

New Podlings

• Asyncband
• Maka
• NullAway

Podlings that failed to report, expected next month

• None

Graduations

• Iggy

The board has motions for the following:

• ResilientDB

Releases

The following releases entered distribution during the month of August:

• TODO

IP Clearance

• none

Legal / Trademarks

• N/A

Infrastructure

• N/A

Table of Contents

Auron BifroMQ KIE OpenServerless Ossie Otava OzHera PouchDB

Auron

Auron accelerates Apache Spark SQL by providing an alternative vectorized execution layer implemented in Rust, enabling native performance while maintaining full Spark compatibility.

Auron has been incubating since 2025-08-05.

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?

Following community discussions and voting, we believe the Auron project has largely met the graduation criteria, and intend to initiate a formal discussion within the Incubator.

How has the community developed since the last report?

1. Elected 4 new committer: Hai Zhou, Huawen Gui, Weiqing Yang, Ming Wei

2. Elected 2 new PPMC member: Ruilei Ma, Shilun Fan

3. Community presentations and outreach continued:

   Yizhong Zhang presented a Auron talk at Apache DataFusion Meetup Shanghai 2026

   Li Zhang presented a Auron talk at Community Over Code Asia 2026 in Beijing, August 8

How has the project developed since the last report?

● Released Apache Auron v8.0.0-incubating on 2026-07-22.

● 82 commits since the last report, including significantly expands Flink integration, native scan support for Apache Iceberg, Apache Hudi, and Apache Paimon, native expression and function coverage, cross-version compatibility, and runtime reliability.

● Completed a brand-new independent registration for the Auron WeChat account. This account will be managed collectively by Auron PMC members moving forward.

● Fixed the minor website defects mentioned by Justin and Calvin, also carried out a full-site brand compliance self-inspection afterward to eliminate similar hidden issues.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Commentary: The project has established a regular Apache release cadence and has completed the maturity model. As summarized in the community graduation discussion, the community has 21 committers including mentors, from more than 13 different companies, with 15 PPMC members and 67 contributors. During incubation, Auron made 3 releases in 11 months with 3 different release managers, used in production by 10+ well-known entities. The project has opened 791 issues with 683 resolved, and 1655 PRs with 1621 merged or closed.

Date of last release:

2026-07-22 (Apache Auron v8.0.0-incubating)

When were the last committers or PPMC members elected?

The most recent committer was Ming Wei and Weiqing Yang, elected in August.

The most recent new PPMC member was Ruilei Ma, elected in August.

Have your mentors been helpful and responsive?

Yes. The mentors have been helpful and responsive. The mentors provided guidance for the graduation discussion. No open issues at this time.

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

Yes. The PPMC is actively managing the Apache Auron (Incubating) brand and trademarks. The PPMC has fixed several branding issues related to WeChat official account and minor website defects. There are no known open brand or trademark issues at this time.

Signed-off-by:

•  (auron) Becket Qin Comments: Looking forward to graduation
•  (auron) Calvin Kirs Comments: Graduation vote in progress
•  (auron) Hao Ding Comments: looking forward to the graduation
•  (auron) Nicholas Jiang Comments: Looking forward to graduation

IPMC/Shepherd notes:

BifroMQ

BifroMQ is a Java-based, high-performance, distributed MQTT broker with native multi-tenancy support, designed for large-scale connections and message delivery.

BifroMQ has been incubating since 2025-04-22.

Three most important unfinished issues to address before graduating:

1. Add more active committers and PPMC members from outside the original team.
2. Make the next Apache release and involve more PPMC members in the release process.
3. Expand the community user base and improve project visibility

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?

liaodongnian (GitHub: @liaodn) completed onboarding as a committer and PPMC member, and contributed a fix for API store-range boundary encoding.

Contributors improved the project website and documentation, including MQTT guidance, the security model, and site discovery.

Joined the open-source marketplace at Community Over Code Asia 2026 in Beijing.

How has the project developed since the last report?

Received issue reports from external users. 4 of the 7 PRs merged in the main repository were contributed by people outside the original team.

Website work covered documentation, search discovery, ASF-hosted Matomo,navigation fixes, and build checks.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

2026-01-28

When were the last committers or PPMC members elected?

2026-06-04: liaodongnian (GitHub: @liaodn) completed onboarding as a committer and PPMC member.

Have your mentors been helpful and responsive?

Our mentors have been helpful and responsive.

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

BifroMQ trademark has been transferred to ASF. We are not aware of any third-party misuse of the BifroMQ name or brand.

Signed-off-by:

•  (bifromq) Christofer Dutz Comments:
•  (bifromq) Xiangdong Huang Comments:
•  (bifromq) Calvin Kirs Comments:
•  (bifromq) Penghui Li Comments:
•  (bifromq) Sheng Wu Comments:

IPMC/Shepherd notes:

KIE

KIE (Knowledge is Everything) is a community of solutions and supporting tooling for knowledge engineering and process automation, focusing on events, rules, and workflows.

KIE has been incubating since 2023-01-13.

Three most important unfinished issues to address before graduating:

1. Readjust CI for 10.3.0 - supposed to be a release will be completely clean of Category X

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

Nope.

How has the community developed since the last report?

New committers elected. New release 10.2.0

How has the project developed since the last report?

A huge unification of repositories been made, that aims to simplify our build system. Supposed to have all Category X code and dependencies removed.

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

When were the last committers or PPMC members elected?

2026-07-23 - Committer

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.

Overall slow progress towards graduation. True that our reports are often a bit behind.

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:

•  (kie) Brian Proffitt Comments: We should start making a targeted list of incubation hurdles to cross (if any) to get this over the line to TLP
•  (kie) Claus Ibsen Comments:
•  (kie) Andrea Cosentino Comments:

IPMC/Shepherd notes:

OpenServerless

OpenServerless is an open source, cloud-agnostic, serverless platform. It offers a complete environment for serverless applications development, based on Kubernetes. With Apache OpenWhisk as its FaaS engine, it provides an unified developer experience with a plethora of services (SQL or noSQL databases, key-value stores, object storage, LLMs services, function schedulers) managed by the platform's core: the operator, along with tooling (the CLI) to simplify (and interact with) deployments, integrated ide and starter application and optimized runtimes integrated with the staters.

OpenServerless has been incubating since 2024-06-17.

Three most important unfinished issues to address before graduating:

1. Complete the next Apache release and improve the release process.

2. Grow the contributor base and elect more committers/PPMC members.

3. Move more design, release, and community discussions to the public dev mailing list.

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

The project has remained active, but much of the work has happened behind the scenes. There are two main reasons for this: the project is heavily structured around submodules, and many developers still coordinate through WhatsApp and private meetings.

This is not aligned with the Apache Way. Unless we actively ask contributors to move discussions to email, people tend to continue using chat messages instead of the public mailing list. This creates a real problem in how project activity is perceived.

The developers who have contributed code recently are:

• Michele Sciabarra
• Bruno Salzano
• Michele Manzani
• Daniele Cremonini
• Francesco Tiberi

Alessio Marinelli also proposed merging a significant new feature, a Spark operator, which we decided to postpone to a later phase.

How has the community developed since the last report?

• We added a new committer, Michele Manzani.
• We have seen new contributions through direct pull requests to the OpenServerless MCP repository.
• A book on OpenServerless has been written by Alessio Marinelli and is currently under review by Manning.

The project is still somewhat overlooked. However, it is the engine behind other open source products expected to launch soon, including an open source vibe-coding engine similar to Lovable.dev, and it has been adopted by the Italian Government Cloud. For these reasons, we expect the community to grow.

The Italian government adoption is expected to be finalized by 2026-12-31, and the Lovable-like project is expected to launch by 2026-09-30.

How has the project developed since the last report?

We worked hard to prepare the first release. The build has been completely reorganized to allow for a complete, standalone source build. The source build is ready, builds successfully, and passes the tests. Some PPMC members tried it and verified that it works, but some additional changes were required:

Changes completed: rebranding and properly addressing security issues. Changes still to do: rebuild the images using tags that comply with ASF usage rules, and document the contributing process.

We expect to call the vote for the first release as soon as those issues are solved.

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:

When were the last committers or PPMC members elected?

One new committer was elected in July 2026.

Have your mentors been helpful and responsive?

Honestly, there has been some tension. We believed things were progressing acceptably, but later understood that the podling was at risk because we had not completed an Apache source release. We had mistakenly treated regular Docker image publication and repository updates as sufficient release activity.

In hindsight, we should have understood the Apache release expectations much earlier. Once the issue became clear, we rushed to prepare a source release and made substantial progress, though several additional problems surfaced near the end.

We did the work together, made mistakes, and were corrected. Some of the feedback was difficult for us to receive, especially given our limited experience with the Apache release process, but we understand that the release requirements are important.

The project is complex, and we still believe it has strong potential. With the emergence of Private AI, the need for private serverless infrastructure is growing, and we believe OpenServerless can become a large and widely used project as significant use cases emerge.

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

The PPMC is working on this and will continue to review the website, documentation, repository, and release materials for Apache branding and trademark requirements.

Signed-off-by:

•  (openserverless) Bertrand Delacrétaz Comments:
•  (openserverless) Enrico Olivelli Comments:
•  (openserverless) François Papon Comments: The release process is on the way but need some works to be mastered by the podling.
•  (openserverless) Jean-Baptiste Onofré Comments: We are discussing with the podling to accelerate on releases, security reports and community grow. That's important "questions" for me on the podling right now.
•  (openserverless) PJ Fanning Comments: Some progress towards a first RC. The initial attempt was added without signing files and digest files and no vote email was sent.

IPMC/Shepherd notes:

Ossie

Apache Ossie comes from Open Semantic Interchange. It is an open specification that defines a vendor-neutral format for expressing business metrics, dimensions, and their relationships. It enables any tool to consume and produce semantic definitions without loss of meaning.

Ossie has been incubating since 2026-06-19.

Three most important unfinished issues to address before graduating:

1. Complete the migration onto ASF infrastructure (git, dev/private mailing lists, website/DNS, issue tracking) and retire the legacy OSI resources; complete IP clearance / Software Grant so the spec and codebase are cleanly under the ASF. This is almost done, final checks are in progress.
2. Produce a first Apache release of the specification (and reference tooling) following ASF release policy — establishing a repeatable, mentor-verified release process with correct LICENSE/NOTICE and source-release conventions. (Spec is currently at v0.1, pre-Apache-release.)
3. Grow a diverse, independent contributor and PPMC base beyond the founding vendors, and demonstrate that spec/roadmap decisions are made in public via the Apache Way (discussion + lazy consensus / votes on dev@). We are happy to see already new contributors.

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

None at this time.

How has the community developed since the last report?

• The multi-vendor coalition behind Ossie continues to broaden: the contributor/participant base has grown past 50 organizations, well beyond the original launch partners.
• Kyvos, Veezo, SAAL, Honeydew, Saiku, Wingarc1st, Gravity, XSOLCORP, PuppyGraph, ThoughtSpot joined the Ossie ecosystem.
• Several Working Groups remains active, shaping proposals to evolution in the Spec.
• Public rename/incubation announcements (OSI -> Apache Ossie) went out via the project blog and partner channels, driving dev@ subscriptions and awareness.

How has the project developed since the last report?

• The apache/ossie repository is active on ASF infrastructure (the codebase predates incubation: 100+ commits and 35+ merged PRs since the repo opened in Nov 2025 as OSI).
• Work has centered on the ASF governance/infrastructure transition and on the specification roadmap: an expression-language spec, advanced metric logic (windowing, complex relationships), additional platform converters, a standardized semantic-query spec, and Apache Polaris integration for catalog-level discoverability of semantic models.
• We already received contributions for several new converters from different models, using different technologies (Python, Java).

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:

None yet — no Apache release has been made since entering incubation.

When were the last committers or PPMC members elected?

• Initial committers (12) and PPMC (7) were seeded at the start of incubation (2026-06).
• Josh Klark has been added to the PPMC on 2026-08-04
• Yong Zheng has been elected as committer on 2026-08-25

Have your mentors been helpful and responsive?

Yes

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

The project was deliberately renamed from OSI to "Ossie" ahead of incubation to avoid acronym confusion. The project name search has been done and approved by ASF Trademark team (see https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-254). The PPMC is carefully managing the brand/trademark.

Signed-off-by:

•  (ossie) Jean-Baptiste Onofré Comments:
•  (ossie) Zili Chen Comments:
•  (ossie) Russell Spitzer Comments:
•  (ossie) Holden Karau Comments:

IPMC/Shepherd notes:

Otava

Otava, a command-line tool, written in Python, that detects statistically significant changes in time-series data stored either in databases or CSV files.

A typical use-case of Otava is as follows:

A set of performance tests is scheduled repeatedly, such as after each commit is pushed. The resulting metrics of the test runs are stored in a time series database (Graphite) or appended to CSV files. Otava is launched by a Jenkins/Cron job (or an operator) to analyze the recorded metrics regularly. Otava notifies about significant changes in recorded metrics by outputting text reports or sending Slack notifications. Otava is capable of finding even small, but persistent shifts in metric values, despite noise in data. It adapts automatically to the level of noise in data and tries to notify only about persistent, statistically significant changes, be it in the system under test or in the environment.

Otava has been incubating since 2024-11-27. Otava entered Incubation as Hunter.

Three most important unfinished issues to address before graduating:

1. Establish frequent releases as a routine, repeatable process.

2. Improve documentation to lower the entry barrier for users and contributors.

3. Define and document the desired long-term architecture, keeping the core library lightweight, making integrations pluggable, and stabilizing the public API before a 1.0.0 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?

• Five external contributors had changes merged across the main and website repositories. Four contributed to the main repository, and a new contributor proposed a website and documentation overhaul on dev@ and delivered significant website improvements.

• The Playground website is now running at playground.otava.apache.org. It provides a public way to compare Otava with other change-detection approaches.

• External contributions covered the core library, integrations, documentation and the project website.

• No new committers or PPMC members were announced during this period.

How has the project developed since the last report?

• Continued refactoring the internal architecture toward a stable public Python API and a clearer separation between the core library, persistence, reporting, and external integrations.

• Expanded and simplified data-source integrations, including support for InfluxDB and more consistent command-line configuration.

• Improved correctness, maintainability, and release readiness through additional tests, typing fixes, dependency updates, and CI maintenance.

• Improved documentation and the newcomer experience through a buildable documentation site, a redesigned project website, and clearer links to the public Playground.

• Enhanced the Playground website to make comparisons between change-detection algorithms easier to explore.

• No new release was made during this reporting period.

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

When were the last committers or PPMC members elected?

Denis Shchepakin was elected as a PPMC member in March 2026.

Have your mentors been helpful and responsive?

Yes

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

no answer

Signed-off-by:

•  (otava) Dave Fisher Comments:
•  (otava) Enrico Olivelli Comments:
•  (otava) Lari Hotari Comments:
•  (otava) Mick Semb Wever Comments:

IPMC/Shepherd notes:

OzHera

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

OzHera has been incubating since 2024-07-11.

Three most important unfinished issues to address before graduating:

1.Complete the next Apache release and improve the release process.

2.Grow the contributor base and elect more committers/PPMC members.

3.Move more design, release, and community discussions to the public dev mailing list.

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

No issues require IPMC or Board attention at this time. We are currently handling our first security vulnerability report. Our mentors have already provided remediation guidance, and we are carrying out the fix according to their advice.

How has the community developed since the last report?

• The project continued to receive steady contributions from around five active contributors during this period (xs3508198, Xue, EricDing, lhhhhf, dingtao).
• Merged several PRs focused on release hygiene and quality: unifying/updating dependency versions, correcting Apache license file headers, removing SNAPSHOT dependencies from the intelligence module, cleaning up private dependency packages, and SQL/query optimizations (e.g. #663, #666, #667, #669, #672, #674).
• We did not elect new committers/PPMC members this period; growing the contributor base and identifying committer candidates remains an active focus.

How has the project developed since the last report?

• Published Apache OzHera 2.2.6-incubating on 2026-06-17, our latest incubating release, with incremental improvements to the release process.
• Since the release, work has centered on commit-by-commit review and codebase cleanup (dependency alignment, license headers, removing SNAPSHOT/private dependencies).
• A SQL injection vulnerability was identified in the 2.2.6-incubating release. The community is now remediating it, and this is the first time the project is following the Apache security/vulnerability-handling process end to end.
• We plan to publish the next incubating release in mid-October 2026, which will deliver new features together with the fix for this vulnerability.

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

When were the last committers or PPMC members elected?

One new committer was elected in April 2026.

Have your mentors been helpful and responsive?

Yes, our mentors have been helpful and responsive. For our current SQL injection vulnerability fix — the first time the project is going through the Apache security-handling process — our mentors have already provided guidance, and we are carrying out the remediation according to their advice. No issues are currently falling through the cracks.

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

The PPMC is working on this and will continue to review the website, documentation, repository, and release materials for Apache branding and trademark requirements.

Signed-off-by:

•  (ozhera) Yu Xiao Comments:
•  (ozhera) Yu Li Comments:
•  (ozhera) Kevin Ratnasekera Comments:
•  (ozhera) Duo Zhang Comments:

IPMC/Shepherd notes:

PouchDB

PouchDB is an open-source JavaScript database inspired by Apache CouchDB that is designed to run well within the browser.

PouchDB has been incubating since 2025-04-15.

Three most important unfinished issues to address before graduating:

1. Completing the ASF incubation process
2. Grow the PouchDB community and form better connections with sporadic contributors
3. More and quicker 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?

• The project is regularly receiving contributions from a handful of regulars and the occasional new contributor, and we are also receiving good-quality issue reports.
  • There is gradually more regular activity in the Slack channel, and semi-regular triage meetings to work through the issue backlog.
  • Added a new PPMC member (see below)
  • Omitted from the last report was a well-received PouchDB presentation we did at FOSDEM in Brussels early 2026, notes and videos here: https://fosdem.org/2026/schedule/event/SDHGJY-local-first-meet-pouchdb-couchdb/

How has the project developed since the last report?

We are making good progress in four areas:

• Moving the project towards replacing the underlying storage adapter in a future release, which will allow us to remove a lot of outdated dependencies and slim down the codebase
• General modernisation of the codebase
• We've completed migrating the website/docs to a modern system that is easier to set up, use and onboard contributors to
• We've completed the move of the website to ASF domains and updated the site to fulfill the ASF website requirements

Specific highlights:

• Incorporated a new Node SQLite storage adapter, this step lays the groundwork for deprecating and removing the LevelDB Subsystem that PouchDB currently depends on, and that we want to move away from. This will shrink the codebase and number of dependencies, and generally make the project more nimble and easier to maintain.
• Completed migration of the old website and documentation from Ruby/Jekyll to JavaScript/Eleventy for a modern developer experience in the same language as the project itself, lower barrier to entry, less setup hassle and faster builds. This included a new build and automatic deployment pipeline that deploys to https://pouchdb.apache.org on merge to main.
• The project website also now adheres to the ASF project and podling requirements, incorporating the ASF/incubator logos and mentioning the ASF and incubator in various places. The site code was also modernized to drop some older dependencies, and no longer relies on external CDNs for assets and libraries.
• Fixed flaky tests with unpredictable timeout errors, which improved DX a lot and made most CI runs much faster.
• Built out a new "versioned documentation" feature to allow docs per release, the same way CouchDB does it, with versioning by release, stable and latest. This is technically ready, we are currently in the process of backfilling the last few version's docs and updating/rewriting the most recent release's documentation, guide and learning pages.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

We're gradually aligning our processes with ASF expectations, but we don't have a mailing list culture and this form of communication and organization takes a bit of getting used to. Mailing list volume is low for that reason. Apart from that, we've made a lot of progress in terms of aligning our public communication with ASF policies, and are in the process of adapting our release procedure. This is rather involved and takes longer than expected.

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

Date of last release:

Jun 21, 2024 (pre-incubation). However, we are currently preparing a 9.1.0 release with the new SQLite storage layer, with the goal of making it an ASF release with a WIP-release disclaimer.

When were the last committers or PPMC members elected?

August 4th, 2026 Alex Feyerke (@espy)

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.

They have been, 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?

Yes, there are no issues to report, see here: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-260

Signed-off-by:

•  (pouchdb) PJ Fanning Comments: Dev list very quiet. GitHub activity in decline (compared with Spring 2026).
•  (pouchdb) Jean-Baptiste Onofré Comments:

IPMC/Shepherd notes: