Re: [DISCUSS] Apache AGE for Postgres 12 - Version

[Eya Badal]

Thank you, everyone, for your great suggestions and feedback. 

Based on the votes and recommendations, I am closing this discussion; we will 
choose 1.1.0 prefix for this release. 

Thank you again, 
Eya



On 2022/09/29 19:18:07 Eya Badal 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 
> 

Re: [DISCUSS] Apache AGE for Postgres 12 - Version

[Dehowe Feng]

I think 1.1.0 would be an appropriate name in this case.

On 2022/09/29 19:18:07 Eya Badal 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 
> 

Re: [DISCUSS] Apache AGE for Postgres 12 - Version

[Mazen Al-Zubairi]

My opinion is that since we'll have an AGE extension for each postgre
database then we can consider the AGE extension to have the same database
version number so I suggest making it like this AGE12 1.0.0 as the first
version regardless of the AGE 11 that is dependent on. with my respect for
all of the opinions.


Thanks to give us a space to share our thoughts.


Regards.


On Thu, Sep 29, 2022, 10:18 PM Eya Badal  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
>

Re: [DISCUSS] Apache AGE for Postgres 12 - Version

[John Gemignani]

It is also likely, for a little while at least, that AGE 11 will have more
current features and fixes than 12 or successive versions.

We are definitely going to need to come up with a process to address
features and fixes being added in and propagated through the appropriate
versions.

john

On Fri, Sep 30, 2022 at 1:14 AM Muhammad Shoaib 
wrote:

> 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
>  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 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  > >> > 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
> > >
> >
> >
>

Re: [DISCUSS] Apache AGE for Postgres 12 - Version

[Muhammad Shoaib]

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
 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 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  >> > 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
> >
>
>

Re: [DISCUSS] Apache AGE for Postgres 12 - Version

[Pieterjan De Potter]

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 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 > 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

Re: [DISCUSS] Apache AGE for Postgres 12 - Version

[Dmitry Dorofeev]

Hi,

I think that the same functionality should have the same version.

So, I vote for the 1.1.0

-D.

On 29.09.2022 22:18 PM, Eya Badal 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

Re: [DISCUSS] Apache AGE for Postgres 12 - Version

[Jasper Blues]

I think it should be versioned after the main development/R 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  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 



smime.p7s
Description: S/MIME cryptographic signature

[DISCUSS] Apache AGE for Postgres 12 - Version

[Eya Badal]

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