3.13.0beta1 ?

Paul Ramsey pramsey at cleverelephant.ca
Fri Aug 16 08:39:38 PDT 2024


Mergemergmerg.

> On Aug 16, 2024, at 8:30 AM, Regina Obe <lr at pcorp.us> wrote:
> 
>> So while I don't get to vote, I think "cmake >= 3.16.0" is a non-event and just
>> fine (given that we already have cmake instead of autoconf :-).
> 
> Greg,
> 
> Thanks for the feedback.  At this point I'm a -0 at this after having many people whining about how
> I'm overreacting over nothing.
> 
> My main issue was not that we should care about people running cmake < 3.16
> But that we shouldn't be making these kind of changes in the 11th hour before beta release.
> 
> It just sets a bad feel in my stomach is all for anyone who is impacted (which may be none), who have been following the progress of GEOS 3.13 and suddenly they can't compile beta.
> And GEOS has a very short cycle from beta to release. So we are talking about less than a month.
> 
> I also look at what we gain, yah we get to remove a bunch of croft, so what, lets just remove more croft that's about it.
> 
> I'm more fine with Howard's recent proposal to up C++ for GEOS 3.14  https://github.com/libgeos/geos/pull/1144 , because he's doing that very early in cycle.
> A whole years time for people who are impacted to decide how this affects their plans.
> 
> Thanks,
> Regina
> 
> 
> 
> 



More information about the geos-devel mailing list