What's the Status of Apache AGE?

[thomastthai]

If you're wondering:

• Is Apache AGE dead?
• Why has development slowed down significantly?
• Why aren’t PRs being approved?
• I have a project that relies on AGE—should I be concerned about its future?

These are valid concerns given the current state of the project. Thanks to @jrgemignani for providing clarity in Issue #2111.

TL;DR

• In early October 2024, Bitnine/AGEDB dismissed the entire development team responsible for contributing to Apache AGE. As a result, project priorities have naturally shifted, leading to a slower pace of development.
• The Apache Software Foundation (ASF) and Bitnine/AGEDB are still working to resolve ongoing disagreements. Jeff, Chair of the Apache AGE Committee, has dedicated significant time to these efforts.
• @jrgemignani and a few others are working to bring PostgreSQL 17 support to version 1.5.0, aiming for completion by the end of the month. However, this may initially be released only as a branch rather than an official release, as full releases require extensive effort, PMC input, and approval from members with the necessary access.

[jeffjirsa]

While I appreciate the effort to summarize state for those who are interested, I think the second bullet point isn't necessary / relevant for most users. The fundamental purpose of the ASF is to product open source software for good in a vendor-neutral fashion, where the project is owned and maintained by the foundation, and contributions happen by individuals. That's not changing.

Individual activity increases and decreases with life situations. The AGE project management committee has an expectation (indeed, an obligation) to continue working with the community, though they're volunteers and that time commitment may vary over time as individual priorities change.

If folks have features, changes, or fixes they'd like to see incorporated, please continue to send PRs, and the project will work to review / merge. If you're interested in contributing more often, please help contribute, including review / testing other submissions - that feedback helps!

[saqib-ali]

Hi. Are there are any plans for Apache AGE to pivot to support ISO/IEC 9075-16:2023 (SQL/PGQ) or ISO/IEC 39075:2024 (GQL)?

[jtomek]

The conversation in here #2111 and vagueness around the issues is concerning.
Please clarify the status and future of this project.

[jrgemignani]

@jtomek I thought that @thomastthai and @jeffjirsa made it as clear as currently possible? But, just in case, I will add a few, maybe clarifying, comments.

There are actually a lot of positive things that are going on in the background that just isn't seen by the public. Much of it I am currently not at liberty to discuss. Additionally, there is ongoing work to bring in PG17 support. But, this work won't necessarily show up in the issues and it will take some time.

@jeffjirsa Stated this well,

Individual activity increases and decreases with life situations. The AGE project management committee has an expectation (indeed, an obligation) to continue working with the community, though they're volunteers and that time commitment may vary over time as individual priorities change.

Hope this is helpful