[geos-devel] PSC Vote: RFC 11 Geos Versioning and EOL Policy

[Paul Ramsey]

+1

> On Sep 19, 2022, at 1:28 PM, Regina Obe <lr at pcorp.us> wrote:
> 
> I am resending this again since no one bothered to vote.
> 
> +1 from me. 
> Sandro already gave a  remark about "You made this voting business a second job. Why don't you just do things and eventually we rage and cut your head?"
> 
> I'll keep that in mind next time I want to push something I know Sandro will not agree with :)
> 
> Below is my request again.
> If no one has an opinion against by EOD, I will mark the motion passed and make the adjustments accordingly.
> 
> Thanks,
> Regina
> 
> -------
> 
> 
> Here is my formal request to vote on:
> 
> https://libgeos.org/development/rfcs/rfc11/
> 
> To accompany that change we will 
> 
> 1) Put a link on https://libgeos.org/usage/download/  to that policy.
> 2) Put in a Final Release Date column on the download page (maybe
> color-coded, though not sure how to color code in markdown so maybe we'll
> skip that)
> Red - past EOL
> Yellow - EOL eminent
> Not sure it's worth to color code newer
> 
> 3) For releases not reached EOL yet, set the expected EOL to 3-4 years from
> the .0 release.
> 
> Not sure what to do with 3.6 and 3.7, both are passed 4 years
> 
> 3.6.0 was released 2016-10-25 (more than 5 years ago) (Dan mentioned this is
> still in Ubuntu LTS 18, which will be eol'd in April 2023), do we wait or
> just EOL it now.
> 
> 3.7.0 was released 2018-09-10  -- about 4 years ago, so I would consider
> this on the potential chopping block given the above proposed policy.
> 
> 
> Thanks,
> Regina
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> geos-devel mailing list
> geos-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geos-devel