Hi Pertejan, Currently this is not the case. However, in the future new versions might have more features than older versions.
I'll support the following 1. for PG 11, AGE_11_1.1.0 2. for PG 12, AGE_12_1.1.0 Kind regards Shoaib On Fri, Sep 30, 2022 at 9:52 AM Pieterjan De Potter <[email protected]> wrote: > Dear Everyone, > > I too think it would be nice to have similar version numbering for > similar feature sets. > > One question that could make this impossible though: will there be > future features that will only be implemented for some versions of > Postgres (11, 12, 13, 14, 15, ...) because of underlying features > supported by those particular Postgres versions? Or would that at that > point be a reason to stop support for Postgres versions that don't > support these underlying features? > > Kind regards, > Pieterjan > > > On 29.09.22 21:23, Jasper Blues wrote: > > I think it should be versioned after the main development/R&D version. > > > > *Reasons: * > > * > > * > > > > * It is easy to tie back to what this version was based off, without > > looking up an index (which could be prone to error). > > * If there is an as yet unfixed edge case bug affecting some portion > > of users on a particular version+pgVersion, they may have some > > confidence about what up/downgrade version to try should they also > > want to up/downgrade Postgres. > > * Simplicity : It is one of the core XP values along with > > communication, feedback, courage and respect. > > > > > > > >> On Sep 30, 2022, at 5:18 AM, Eya Badal <[email protected] > >> <mailto:[email protected]>> wrote: > >> > >> Dear Everyone, > >> > >> We are planning on our first release of Apache AGE for Postgres 12. It > >> will be based on the Apache AGE 1.1.0 release that supports Postgres > >> 11. There will be a prefix for this release and all Postgres 12 > >> supported releases. > >> > >> However, since this is the first Postgres 12 release, should the > >> version be 1.0.0 or 1.1.0 because it is based on the 1.1.0 release for > >> Postgres 11? > >> > >> Please share your thoughts and suggestions. > >> > >> Thank you very much, > >> Eya > > > >
