3.14 Release Calendar

[Paul Ramsey]

Yes, as a general rule at this time of year I'm going to be calling
for a beta so we can move into the packaging stage, with the goal of
having all the parts released by early September, and to have betas of
everything released even before that, so that everything ends up
packaged with the late-Sept/early-Oct PgSQL release date. At our
current development cadence, a yearly major release seems to serving
us well. I haven't given thought to a cadence for stable branch
releases, I wonder if we should put a calendar on that too.

P

On Thu, Jul 10, 2025 at 6:37 AM Daniel Baston <dbaston at gmail.com> wrote:
>
> That makes sense. I haven't been following Postgres development, so I
> wasn't aware. In the future, is it fair to say that we should expect a
> GEOS beta ~ 2 months after a Postgres beta? And a GEOS feature freeze
> N weeks before the beta?
>
> Dan
>
> On Wed, Jul 9, 2025 at 10:55 AM Paul Ramsey <pramsey at cleverelephant.ca> wrote:
> >
> >
> >
> > > On Jul 9, 2025, at 5:15 AM, Daniel Baston <dbaston at gmail.com> wrote:
> > >
> > > I'd like to finish #1268 and #803 at least. I thought we were
> > > releasing in the fall?
> >
> > Well, my goal as always is to hook up all the cars in the release train. To get widely packaged and deployed into clouds after the PgSQL 18 release, PostGIS needs to be in release when that happens, and to finalize PostGIS 3.6 for release, GEOS 3.14 needs to be in release.
> >
> > So I’d like to get a beta out so we can get run through the packaging grinder in July, with a final release in early August.
> >
> > P.
> >
> >
> > >
> > > Dan
> > >
> > > On Wed, Jul 9, 2025 at 6:56 AM Paul Ramsey <pramsey at cleverelephant.ca> wrote:
> > >>
> > >> It's coming up on time to do the annual release! We have the progress
> > >> meter in flight, and anything else that needs to complete before
> > >> release?
> > >>
> > >> https://github.com/libgeos/geos/pulls
> > >> https://github.com/libgeos/geos/issues
> > >>
> > >> If everything is looking OK, I will go ahead and tag a beta for
> > >> packaging and testing.
> > >>
> > >> P.
> >