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

Reply via email to