Hi Taylor,
Thank you for your interest in Apache AGE!
Our goal is to have a complete version of AGE for each supported version of
PostgreSQL. That is our goal. I'm sorry if that sounded too much like
marketing talk.
As our project has grown a lot in the past few months and years, we have
had to reassess our versioning, branching, support, and CI strategies. What
you are seeing right now is our team trying to iron out a lot of these
issues in real time.
So, to address your questions, given that quick background,...
For the "pre-release" tags, we are still cleaning up our release procedure
documents and process and this item needs to be addressed and clarified.
The page that you linked is outdated and needs to be corrected as well.
Thank you for bringing this to our attention.
The distinction between pre-release and release is, before and after the
Apache vote, for the official release; assuming it was successful. It
appears that was overlooked in the documentation and it too needs to be
updated. Thank you for bringing this to our attention as well. Btw, for
clarification, the latest release should be the highest PostgreSQL version
of AGE.
There are separate releases for each version of PostgreSQL due to,
sometimes significant, changes between the different versions of
PostgreSQL. For example, PostgreSQL 11 and 12 are significantly different
due to the removal of OIDs. This created a huge undertaking to rewrite code
to address those changes.
Our policy is to drop off support of versions of PostgreSQL as PostgreSQL
drops support for them. As for newer versions, we are currently trying to
catch up to the latest fully released versions of PostgreSQL. After we
reach that point, we will need to work out the best strategy for the beta
versions of PostgreSQL.
As for a timeline or timeframe for PostgreSQL 14 and 15 support: 14 is
nearly ready, 15 is close behind. I would rather not give anything more
specific than that because something inevitably happens to cause delays.
For example, right now we are finishing off some significant features and
bug fixes in the master. We will then be propagating them to all supported
PostgreSQL versions and then 14 and 15.
For clarification, the latest versions of AGE are 1.3.0 and are available
for PostgreSQL 11, 12, & 13.
Hopefully this helps cover all of your questions. If not, please let me
know.
I should point out that our policies are always subject to change if a
better approach is found.
john
On Mon, Jun 26, 2023 at 10:09 AM Riggan, Taylor
wrote:
> Hi all,
>
> In reviewing the Release process on the website (
> https://age.apache.org/contribution/process) I'm not seeing any reference
> to "pre-releases". There are currently two pre-releases available on the
> GitHub repo (1.2.0 and 1.3.0) for Apache AGE. What constitutes a release
> being a "pre-release" and when does this become a full "release"?
>
> There are also separate releases for each version of Postgres. What is
> the rationale behind having separate releases for each Postgres release
> versus building a version scheme that mirrors the Postgres versioning?
>
> What is the policy for back-porting bugs/features for older version of
> Postgres? Is there intent to always maintain a version of Apache AGE for
> every version of Postgres starting with v11, or will support for older
> versions drop off at some point? Along those same lines, what is the
> planned cadence (or lag) for keeping up with Postgres versions? Postgres
> is now shipping 16-beta. Which means there are production versions of
> Postgres 14 and 15. When will Apache AGE have support for those versions?
>
> Thank you,
>
> --
> Taylor Riggan
> Sr. Graph Architect | Amazon Neptune | AWS
>
>
