[postgis-devel] EOL 2.2 after 2.2.7

[Darafei "Komяpa" Praliaskouski]

In that logic:

Postgres 9.2 (EOL September 2017) had PostGIS 2.1 to 2.3 as latest at
various points in time,
Postgres 9.3 (EOL September 2018, still alive) had PostGIS 2.1 to 2.4 as
latest,
Postgres 9.4 (EOL December 2019) had PostGIS 2.1 and supported until trunk,
Postgres 9.5 (EOL January 2021) had PostGIS 2.2 and supported until trunk.

Does it mean we can't EOL 2.1 until December 2019, and can't EOL 2.2 until
Jan 2021?

I think a simple rule "we support versions enough to cover all non-EOL
Postgres versions, at least two of them" is more like what we're trying to
say with all the "2-4 years" and "until {newest, oldest} postgres version
is EOL".

пт, 30 мар. 2018 г. в 16:08, Nicklas Aven <nicklas.aven at jordogskog.no>:

> As someone said before. When you do the job to upgrade postgresql major
> version you probably also upgrade postgis. Then, from a user perspective,
> you probably expect Postgis to live as long as the newest postgresql
> version at that point. That means that when people upgraded to pg 9.3 they
> installed postgis  2.2 and probably expect postgis to be supported until
> they are forced to upgrade postgresql.
>
> What the minimum version of postgresql, postgis supports I think anyway
> is irrelevant.
>
> Regards
> Nicklas
>
> Sent from my Sony Xperia™ smartphone
>
> ---- Darafei "Komяpa" Praliaskouski wrote ----
>
> Given that we depend on minimal Postgres versions in our decisions, can we
> give EOL dates for each PostGIS release in advance then?
>
> Basically make a join of
> https://www.postgresql.org/support/versioning/
> and
> https://trac.osgeo.org/postgis/wiki/UsersWikiPostgreSQLPostGIS
>
> This way EOL for 2.2 is EOL of 9.1  -  September 2016
> EOL for 2.3 is EOL of 9.2 - September 2017
> EOL for 2.4 is EOL of 9.3 - September 2018
>
> This way 2.4 lives just for a year though and EOLs with a release of 2.5 -
> is that a desired thing?
> If 2.5 accidentially supports 9.3, shall we EOL it right at release?
>
> пт, 30 мар. 2018 г. в 0:55, Regina Obe <lr at pcorp.us>:
>
>> Yah Darafei mentioned that in IRC.  I guess I've never been good at
>> elementary math.
>>
>>
>>
>> Well I suppose I could bare another release of 2.2, or we change it to
>> 2-4 years or whenever the earliest supported version of a PostgreSQL on a
>> release reaches EOL.
>>
>>
>>
>> So since 2.2 first release supported is 9.1 we can EOL it now. Since 9.1
>> is already EOL'd
>>
>>
>>
>>
>>
>>
>>
>> *From:* postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] *On
>> Behalf Of *Daniel Baston
>> *Sent:* Thursday, March 29, 2018 4:51 PM
>> *To:* PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
>> *Subject:* Re: [postgis-devel] EOL 2.2 after 2.2.7
>>
>>
>>
>> The policy on postgis.net suggests we should support 2.2 for 3-4 years,
>>
>> i.e. until sometime between October 2018 -  October 2019.
>>
>>
>>
>> Dan
>>
>>
>>
>> On Tue, Mar 27, 2018 at 1:42 PM, Regina Obe <lr at pcorp.us> wrote:
>>
>> I thought we had EOL'd 2.2, but guess not since we are still testing it
>> and
>> never made an official EOL announcement
>>
>> Everyone okay if I do one more release of 2.2, and then EOL it and take it
>> off our testing menu?
>>
>> Thanks,
>> Regina
>>
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/postgis-devel
>>
>>
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/postgis-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20180330/97a4dc24/attachment-0001.html>