From pramsey at cleverelephant.ca  Thu Jun 11 13:30:45 2026
From: pramsey at cleverelephant.ca (Paul Ramsey)
Date: Thu, 11 Jun 2026 13:30:45 -0700
Subject: 3.15 release schedule
Message-ID: <CACowWR07sQL4dXparpsAHZsjWLq_MpQwNcECrjUx5fXd0OiMgg@mail.gmail.com>

Hey all, summer time is nearly here, and with it the need to push out
a GEOS release, so I am wondering what you all have cooking that might
want to get added before the release? How do we feel about aiming for
a mid-July release date? Any other concerns or input for this cycle?

P

From lr at pcorp.us  Thu Jun 11 13:48:12 2026
From: lr at pcorp.us (Regina Obe)
Date: Thu, 11 Jun 2026 16:48:12 -0400
Subject: 3.15 release schedule
In-Reply-To: <CACowWR07sQL4dXparpsAHZsjWLq_MpQwNcECrjUx5fXd0OiMgg@mail.gmail.com>
References: <CACowWR07sQL4dXparpsAHZsjWLq_MpQwNcECrjUx5fXd0OiMgg@mail.gmail.com>
Message-ID: <000a01dcf9e3$9ee989f0$dcbc9dd0$@pcorp.us>


> -----Original Message-----
> From: Paul Ramsey <pramsey at cleverelephant.ca>
> Sent: Thursday, June 11, 2026 4:31 PM
> To: GEOS Development List <geos-devel at lists.osgeo.org>
> Subject: 3.15 release schedule
> 
> Hey all, summer time is nearly here, and with it the need to push out a GEOS
> release, so I am wondering what you all have cooking that might want to get
> added before the release? How do we feel about aiming for a mid-July release
> date? Any other concerns or input for this cycle?
> 
> P

I'm good with mid July +1


From dbaston at gmail.com  Thu Jun 11 17:40:57 2026
From: dbaston at gmail.com (Daniel Baston)
Date: Thu, 11 Jun 2026 20:40:57 -0400
Subject: 3.15 release schedule
In-Reply-To: <CACowWR07sQL4dXparpsAHZsjWLq_MpQwNcECrjUx5fXd0OiMgg@mail.gmail.com>
References: <CACowWR07sQL4dXparpsAHZsjWLq_MpQwNcECrjUx5fXd0OiMgg@mail.gmail.com>
Message-ID: <CA+K_q_o3jAnj57Hus-Wu3sY4Fjb4yPduMzvXaqP1RjMQ_P-vMw@mail.gmail.com>

I'm OK with cutting a beta in early July, the big things on my end would be
#1382 (needs to be rebased) and #1427.

Dan


On Thu, Jun 11, 2026 at 4:31?PM Paul Ramsey <pramsey at cleverelephant.ca>
wrote:

> Hey all, summer time is nearly here, and with it the need to push out
> a GEOS release, so I am wondering what you all have cooking that might
> want to get added before the release? How do we feel about aiming for
> a mid-July release date? Any other concerns or input for this cycle?
>
> P
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geos-devel/attachments/20260611/2ba05dad/attachment.htm>

From lr at pcorp.us  Tue Jun 16 16:01:58 2026
From: lr at pcorp.us (Regina Obe)
Date: Tue, 16 Jun 2026 19:01:58 -0400
Subject: Are we good to release GEOS 3.15.0beta1?
Message-ID: <000701dcfde4$22f47850$68dd68f0$@pcorp.us>

Dan,

I noticed you committed your curved changes to main today.

Are we good to release a GEOS 3.15.0beta1 or are there some other
outstanding things people want to commit.

Thanks,
Regina


From lr at pcorp.us  Tue Jun 16 16:19:30 2026
From: lr at pcorp.us (Regina Obe)
Date: Tue, 16 Jun 2026 19:19:30 -0400
Subject: Are we good to release GEOS 3.15.0beta1?
Message-ID: <000801dcfde6$95ba6b40$c12f41c0$@pcorp.us>

> Dan,
> 
> I noticed you committed your curved changes to main today.
> 
> Are we good to release a GEOS 3.15.0beta1 or are there some other
> outstanding things people want to commit.
> 
> Thanks,
> Regina

I guess we are not quite ready for a beta.  I just noticed we still have
some marked for 3.15.0:

https://github.com/libgeos/geos/milestone/24 (some of which related to
curve)


I would like to ask some of these don't look realistic to get in 3.15,
should we push these to 3.16 milestone:

Make prepared geometry (more?) thread-safe:
https://github.com/libgeos/geos/pull/826
HotPixelIndex: Use STRtree instead of KdTree:
https://github.com/libgeos/geos/pull/769
nlohmann_json should (optionally) be pulled in as a package:
https://github.com/libgeos/geos/issues/1292


Then there are some that feel like they should be okay to go in 3.15, but
are not marked as such:

https://github.com/libgeos/geos/pulls

OSS-Fuzz: Move fuzzers upstream and add a new fuzzer targets json
processing: https://github.com/libgeos/geos/pull/1447
Ensure rpath is used for libgeos_c.so:
https://github.com/libgeos/geos/pull/1436

#this one I'm not sure about if people are still reluctant to push this in
though it sounds like it's mostly ready
CoverageSimplify: add progress callback and add
GEOSCoverageSimplifyVWWithProgress_r()
https://github.com/libgeos/geos/pull/1268 

Thanks,
Regina



From dbaston at gmail.com  Tue Jun 16 18:35:32 2026
From: dbaston at gmail.com (Daniel Baston)
Date: Tue, 16 Jun 2026 21:35:32 -0400
Subject: Are we good to release GEOS 3.15.0beta1?
In-Reply-To: <000701dcfde4$22f47850$68dd68f0$@pcorp.us>
References: <000701dcfde4$22f47850$68dd68f0$@pcorp.us>
Message-ID: <CA+K_q_rv7+gf1gt3mDEpWcFnRGD88QgUpkGJfdtNWpTwCJ4GCw@mail.gmail.com>

I'd like to get https://github.com/libgeos/geos/pull/1382 merged, and I
just discovered https://github.com/libgeos/geos/issues/1449 which seems
important.

Dan

On Tue, Jun 16, 2026 at 7:21?PM Regina Obe <lr at pcorp.us> wrote:

> Dan,
>
> I noticed you committed your curved changes to main today.
>
> Are we good to release a GEOS 3.15.0beta1 or are there some other
> outstanding things people want to commit.
>
> Thanks,
> Regina
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geos-devel/attachments/20260616/650d3938/attachment.htm>

From lr at pcorp.us  Tue Jun 16 22:48:18 2026
From: lr at pcorp.us (Regina Obe)
Date: Wed, 17 Jun 2026 01:48:18 -0400
Subject: Are we good to release GEOS 3.15.0beta1?
In-Reply-To: <CA+K_q_rv7+gf1gt3mDEpWcFnRGD88QgUpkGJfdtNWpTwCJ4GCw@mail.gmail.com>
References: <000701dcfde4$22f47850$68dd68f0$@pcorp.us>
 <CA+K_q_rv7+gf1gt3mDEpWcFnRGD88QgUpkGJfdtNWpTwCJ4GCw@mail.gmail.com>
Message-ID: <000501dcfe1c$e700f010$b502d030$@pcorp.us>

Okay.  I marked some things 3.16 that I felt are too risky to put in and some others 3.15.  Feel free to change any of them since you know better than I would.

 

From: Daniel Baston <dbaston at gmail.com> 
Sent: Tuesday, June 16, 2026 9:36 PM
To: Regina Obe <lr at pcorp.us>
Cc: GEOS Development List <geos-devel at lists.osgeo.org>
Subject: Re: Are we good to release GEOS 3.15.0beta1?

 

I'd like to get https://github.com/libgeos/geos/pull/1382 merged, and I just discovered https://github.com/libgeos/geos/issues/1449 which seems important.

 

Dan

 

On Tue, Jun 16, 2026 at 7:21?PM Regina Obe <lr at pcorp.us <mailto:lr at pcorp.us> > wrote:

Dan,

I noticed you committed your curved changes to main today.

Are we good to release a GEOS 3.15.0beta1 or are there some other
outstanding things people want to commit.

Thanks,
Regina

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geos-devel/attachments/20260617/7b0a06c4/attachment-0001.htm>

From pramsey at cleverelephant.ca  Mon Jun 22 09:44:39 2026
From: pramsey at cleverelephant.ca (Paul Ramsey)
Date: Mon, 22 Jun 2026 09:44:39 -0700
Subject: Fuzzers in Repo
Message-ID: <CACowWR3tdHG1iTG7a94SFwTcHbfBTg5qFcJDii6W2Vij5S3+Mw@mail.gmail.com>

https://github.com/libgeos/geos/pull/1447

I am quite tempted by this PR, anyone see any downside to it?

P

From lr at pcorp.us  Mon Jun 22 12:03:34 2026
From: lr at pcorp.us (Regina Obe)
Date: Mon, 22 Jun 2026 15:03:34 -0400
Subject: Fuzzers in Repo
In-Reply-To: <CACowWR3tdHG1iTG7a94SFwTcHbfBTg5qFcJDii6W2Vij5S3+Mw@mail.gmail.com>
References: <CACowWR3tdHG1iTG7a94SFwTcHbfBTg5qFcJDii6W2Vij5S3+Mw@mail.gmail.com>
Message-ID: <000001dd0279$d34bee10$79e3ca30$@pcorp.us>

I don't see a downside.  We are going to release beta first right, so we can always pull it out if it becomes an issue.

> -----Original Message-----
> From: Paul Ramsey <pramsey at cleverelephant.ca>
> Sent: Monday, June 22, 2026 12:45 PM
> To: GEOS Development List <geos-devel at lists.osgeo.org>
> Subject: Fuzzers in Repo
> 
> https://github.com/libgeos/geos/pull/1447
> 
> I am quite tempted by this PR, anyone see any downside to it?
> 
> P


From schwehr at gmail.com  Mon Jun 22 13:40:36 2026
From: schwehr at gmail.com (Kurt Schwehr)
Date: Mon, 22 Jun 2026 13:40:36 -0700
Subject: Fuzzers in Repo
In-Reply-To: <000001dd0279$d34bee10$79e3ca30$@pcorp.us>
References: <CACowWR3tdHG1iTG7a94SFwTcHbfBTg5qFcJDii6W2Vij5S3+Mw@mail.gmail.com>
 <000001dd0279$d34bee10$79e3ca30$@pcorp.us>
Message-ID: <CACmBxytdnwSo5ycncyvwzr5tm-DMm9jvat6L9GsaEyVCaKSXxQ@mail.gmail.com>

Notes: I am speaking for myself - not for Google and not for any open
source project.  I'm a Google employee (but not associated with OSS Fuzz)
and on the board for GDAL.

GDAL has the fuzzers in the repo. It works well and gives the project more
direct control, so I'm very much for it moving into GEOS.

https://github.com/OSGeo/gdal/tree/master/fuzzers

And for some history... I used to run these fuzzers long ago inside Google
before OSS Fuzz got going:

https://github.com/schwehr/gdal-autotest2/tree/master/cpp/third_party/geos/io

On Mon, Jun 22, 2026 at 12:03?PM Regina Obe <lr at pcorp.us> wrote:

> I don't see a downside.  We are going to release beta first right, so we
> can always pull it out if it becomes an issue.
>
> > -----Original Message-----
> > From: Paul Ramsey <pramsey at cleverelephant.ca>
> > Sent: Monday, June 22, 2026 12:45 PM
> > To: GEOS Development List <geos-devel at lists.osgeo.org>
> > Subject: Fuzzers in Repo
> >
> > https://github.com/libgeos/geos/pull/1447
> >
> > I am quite tempted by this PR, anyone see any downside to it?
> >
> > P
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geos-devel/attachments/20260622/781183e3/attachment.htm>