Hrm, probably a artifact of the order in which I tagged things. I wonder if I can force another order...
> On Mar 4, 2025, at 9:23 AM, Kurt Schwehr <schw...@gmail.com> wrote: > > Thanks for all the releases! > > One weirdness: 3.9.6 is marked as "latest" on github. > > https://github.com/libgeos/geos/releases/tag/3.9.6 > > I would think that honor would go to 3.13.1, yes? :) > > https://github.com/libgeos/geos/releases/tag/3.13.1 > > <Screenshot 2025-03-04 at 9.21.07 AM.png> > > On Thu, Feb 27, 2025 at 12:59 PM Paul Ramsey <pram...@cleverelephant.ca > <mailto:pram...@cleverelephant.ca>> wrote: >> Yes, there’s some useful stuff in those changes. >> Any objections to my running off a pile of patch releases? >> >> P >> >> > On Feb 27, 2025, at 1:14 AM, Mike Taves <mwto...@gmail.com >> > <mailto:mwto...@gmail.com>> wrote: >> > >> > Hi All, >> > >> > Looking across the maintenance branches, I see a good number of fixes >> > queued up: >> > >> > - https://github.com/libgeos/geos/blob/3.13/NEWS.md >> > - https://github.com/libgeos/geos/blob/3.12/NEWS.md >> > - https://github.com/libgeos/geos/blob/3.11/NEWS.md >> > - https://github.com/libgeos/geos/blob/3.10/NEWS >> > - https://github.com/libgeos/geos/blob/3.9/NEWS >> > >> > Seems to me it could be time to cut some maintenance releases. >> > >> > Cheers, Mike >>
