[postgis-devel] [geos-devel] End of Life Policy (EOL)

[Regina Obe]

I’ve made the  change to add “generally”

 

 

 

From: Martin Davis [mailto:mtnclimb at gmail.com] 
Sent: Wednesday, September 14, 2022 3:27 PM
To: Regina Obe <lr at pcorp.us>
Subject: Re: [geos-devel] End of Life Policy (EOL)

 

Sounds good to me, Regina.

 

On Wed, Sep 14, 2022 at 12:24 PM Regina Obe <lr at pcorp.us <mailto:lr at pcorp.us> > wrote:

> Martin Davis <mtnclimb at gmail.com <mailto:mtnclimb at gmail.com> > writes:
> 
> > Our development resource bandwidth, and also downstream pipeline size.
> >
> > I think we should have a policy of one minor release per year (if
> > needed) And (try to) make them somewhat scheduled (which we already
> do
> > informally, to align with PostGIS).
> 
In this case, I had specified 1-2 years  following our current behavior.

We could maybe soften that a bit by adding the word "generally" such as
below.

"The GEOS project generally releases a new minor release every 1-2 years.
Each minor release has a git repo dedicated branch for it named after the
minor version."

Our cadence is something I think is useful for users and packagers  of GEOS
to know, so they know when they can expect new features.
As  Greg stated, I would not want to say we absolutely follow this, though I
can't remember a time we haven't pushed out a new minor release for longer
than 2 years.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20220914/ff0e5b78/attachment.htm>