Are we good to release GEOS 3.15.0beta1?

Paul Ramsey pramsey at cleverelephant.ca
Tue Jul 7 08:31:45 PDT 2026


Awesome, so no changes left to CAPI? I will cut the beta1.
P

On Tue, Jul 7, 2026 at 6:36 AM Daniel Baston <dbaston at gmail.com> wrote:
>
> All green now.
>
> On Mon, Jul 6, 2026 at 5:29 PM Regina Obe <lr at pcorp.us> wrote:
>>
>> I see a lot of failed checks in #1466 will you have that fixed soonish?
>>
>>
>>
>> From: Daniel Baston <dbaston at gmail.com>
>> Sent: Monday, July 6, 2026 4:26 PM
>> To: Paul Ramsey <pramsey at cleverelephant.ca>
>> Cc: Regina Obe <lr at pcorp.us>; GEOS Development List <geos-devel at lists.osgeo.org>
>> Subject: Re: Are we good to release GEOS 3.15.0beta1?
>>
>>
>>
>> Think we can squeeze #1466 in for this one? (and #1460 ?)
>>
>>
>>
>> Dan
>>
>>
>>
>> On Mon, Jul 6, 2026 at 11:17 AM Paul Ramsey <pramsey at cleverelephant.ca> wrote:
>>
>> We ready to go?
>>
>> On Tue, Jun 16, 2026 at 6:35 PM Daniel Baston <dbaston at gmail.com> wrote:
>> >
>> > 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
>> >>


More information about the geos-devel mailing list