Re: [geos-devel] C library versioning confusion

On Fri, Dec 11, 2020 at 08:13:42AM -0800, Paul Ramsey wrote: > > > > On Dec 11, 2020, at 8:10 AM, Sandro Santilli wrote: > > > > On Fri, Dec 11, 2020 at 07:47:19AM -0800, Paul Ramsey wrote: > >> Please change the version in the branch and master ASAP. > > > > Done: > > Can you please also fix

Re: [geos-devel] C library versioning confusion

> On Dec 11, 2020, at 8:10 AM, Sandro Santilli wrote: > > On Fri, Dec 11, 2020 at 07:47:19AM -0800, Paul Ramsey wrote: >> Please change the version in the branch and master ASAP. > > Done: > Can you please also fix the step 1) directions in HOWTO_RELEASE Also please look at steps 1 and 9 in

Re: [geos-devel] C library versioning confusion

On Fri, Dec 11, 2020 at 07:47:19AM -0800, Paul Ramsey wrote: > Please change the version in the branch and master ASAP. Done: 15/0/14 for 3.9 16/0/15 for master Whoever installed 3.9.0beta2 will have to do manual cleanups. --strk; ___ geos-dev

Re: [geos-devel] 3.9.0rc1

> On Dec 10, 2020, at 9:47 PM, Sebastiaan Couwenberg wrote: > > On 12/10/20 8:56 PM, Paul Ramsey wrote: >> http://download.osgeo.org/geos/geos-3.9.0rc1.tar.bz2 > > So the geos-3.9.0.tar.bz2 that was there yesterday was a mistake (it's > gone now)? Yes, it was a mistake. P > >> Last chance

Re: [geos-devel] C library versioning confusion

Please change the version in the branch and master ASAP. > On Dec 11, 2020, at 6:19 AM, Sandro Santilli wrote: > > I guess this was done because for some reason the documentation > for version was changed at some point to be inaccurate (ie: "always > increment revision"). I've now committed the

[geos-devel] C library versioning confusion

I've noticed there's some confusion with versioning of the C library. Hoping to do something useful I moved documentation about how to set version directly in Version.txt The confusion I see is with CAPI_INTERFACE_* values. For 3.9.0, like for any other .0 release, the CAPI_INTERFACE_REVISION sho

[geos-devel] Tags out of branches (was: Do you mind a GEOS-3.6.5 release ?)

For the record: the same problem existed in 3.7 branch. I've fixed that as well by also merging there the "3.7.3" tag, latest tag in 3.7 branch --strk; On Fri, Dec 11, 2020 at 12:54:00PM +0100, Sandro Santilli wrote: > I've fixed this myself by merging the "3.6.4" tag into the > "svn-3.6" branch.

[geos-devel] GEOS 3.6.5 released

With some road bumps, GEOS 3.6.5 is now out. The only change since 3.6.4 is a crash in RelateOp when passed collections with EMPTY components (#1085) --strk; () Free GIS & Flash consultant/developer /\ https://strk.kbt.io/services.html ___ geos-

[geos-devel] [GEOS] Batch modify: #810, #806, #805, #737, #861, #844, #864, #848, ...

Batch modification to #810, #806, #805, #737, #861, #844, #864, #848, #682, #859 by strk: milestone to 3.6.6 Comment: Ticket retargeted after milestone closed -- Tickets URL: GEOS

[geos-devel] Do you mind a GEOS-3.6.5 release ?

I've fixed this myself by merging the "3.6.4" tag into the "svn-3.6" branch. I did keep the "merge commit" so to be still able to reference the tagged commit. Now `git branch --contains 3.6.4` will report "svn-3.6" as well. The subject was updated to reflect that next release will be 3.6.5 then, w

Re: [geos-devel] Do you mind a GEOS-3.6.4 release ?

Oops, I found a pre-existing 3.6.4 tag: https://git.osgeo.org/gitea/geos/geos/commits/tag/3.6.4 AND a download from OSGeo ! http://download.osgeo.org/geos/geos-3.6.4.tar.bz2 BUT such tag is NOT reachable from the "svn-3.6" branch, which does NOT contain those commits. Paul: I think this was take

Re: [geos-devel] Do you mind a GEOS-3.6.4 release ?

+1 On Fri., Dec. 11, 2020, 2:34 a.m. Sandro Santilli, wrote: > Release 3.6.3 came out in August 2018. Since then we have these > fixes: > > Changes in 3.6.4 > > - Bug fixes / improvements > - Fix crash in GEOSUnaryUnion with empty LineString > (#928, Sergey Fedoseev) > - Fix in

[geos-devel] Do you mind a GEOS-3.6.4 release ?

Release 3.6.3 came out in August 2018. Since then we have these fixes: Changes in 3.6.4 - Bug fixes / improvements - Fix crash in GEOSUnaryUnion with empty LineString (#928, Sergey Fedoseev) - Fix incorrect error return values in GEOSLength and GEOSisValidDetail (#941, Dan

Re: [geos-devel] 3.9.0rc1 [was: beta2 still needs --enable-overlayng]

Overnight checks on R packages show no new problems - package maintainers were warned of failing tests as soon as OverlayNG was available for testing. Roger On Thu, 10 Dec 2020, Roger Bivand wrote: On Thu, 10 Dec 2020, Paul Ramsey wrote: This is done. There will be an rc1 shortly. Good,