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

[isoctcolo]

Hello one question is there something new or let's say is there a timeline for news about the project?

[jrgemignani]

I am working to get PG17 out there by the end of the month. Other timelines,... I will need to discuss this with the other PMCs to see what we can get out there and clarify more.

[uhayat]

@jeffjirsa I went through the meeting notes of Feb 16 Apache AGE board meeting. I don't see any plan of action to move forward rather an inquiry from PMC to decide the fate of project.

Based on Inquiry, Is there any PMC member willing to be part of release process ?

• If they are why, why we don't see much activity
• If they are not, then whats the way forward

Is putting embargo on a project is Apache Way? Of course not. But surely it does seems like. Nobody is helping project and not letting others to help.
And if there is a little progress, it's slower than snail pace.

Isn't it the time to send call for contribution/collaboration message to public and see how many people willing to help and if nobody is willing to help then move it to attic.
(Its my personal opinion and anybody can disagree)

[jeffjirsa]

Yes, a sufficient number of PMC members indicated they’re interested and involved in both authoring patches, reviewing contributions, and releasing new versions when they’re ready.

We continue to encourage code contributions from existing and new contributors alike.

[jrgemignani]

@uhayat There isn't an "embargo" on Apache AGE. However, due to personal, work, and/or economic reasons, many of the current Apache AGE members are more focused elsewhere. So yes, development will be slower, unfortunately.

As for other contributors/collaborators, we would love to have more. However, it has always been hard finding consistent individuals to contribute to the core code; ones that would stay around long enough to become more than just committers.

And Jeff stated it well -

We continue to encourage code contributions from existing and new contributors alike.

[jrgemignani]

I don't want to jinx it, but I do believe the issues with AGEDB are no more -

The Apache Software Foundation (ASF) and Bitnine/AGEDB are still working to resolve ongoing disagreements.

[isoctcolo]

Sorry to bug you all is there something new on that topic ?

[jrgemignani]

Apache AGE status update -

Apache AGE development is still ongoing. Currently, AGE 1.6.0 is being rolled out to PG17, then PG15, PG14, and possibly PG13. AGE for PG16 has already been released and is available. The master branch is currently on PostgreSQL 17.

Currently, the focus is on the releases, performance improvements, and bugs.

As always, we welcome other developers who are committed to the project!

[thomastthai]

Who has tried to get the current master branch for PostgreSQL 17 work with 18? What challenges, if any, did you encounter?

[jrgemignani]

@thomastthai Could you please create a separate discussion thread for this? I feel like it is a bit off topic.

[jrgemignani]

Unless anyone has a good reason to keep this thread open, I will be closing this thread shortly. It can always be reopened, however, I feel like it has served its purpose.