CAPI version not being updated between micro releases

[strk]

I noticed that the CAPI version is not being update between micro releases in the 3.4.x branch. Specifically it remains 1.8.0 for both 3.4.0 and 3.4.1. It should be fixed and get PATCH level incremented even if nothing changes in the CAPI implementation itself.

[robe]

so it should be 1.8.1 for 3.4.1? for 3.4.2 do we update it to 1.8.1 or 1.8.2?

[strk]

It should have been 1.8.1 for 3.4.1. I'd say we update it to 1.8.2 for 3.4.2, just to keep in sync. The 3.4.0 and 3.4.1 releases should really be marked as broken to discourage spreading...

[robe]

okay I put a note on the home page for 3.4.1 http://trac.osgeo.org/geos/wiki

You want to do the next release. I'm afraid I'm too inexperienced for releasing GEOS. Maybe after a while I can try releasing again, but probably best if you do for now.

[strk]

Don't get discouraged, you're almost done with this :) Just call for help on the mailing list and wait enough time for people to react.

Report what's still blocking, if anything, or what's to be tested.

Thanks a lot for your effort, it's really appreciated.

[strk]

r3906 in 3.4 branch, please test

[gdt]

While I don't object to a micro-bump on releases, it's really important to follow the standard discipline for major (only bump on API withdrawals or incompatible signature changes, and to try really hard not to do that, and never in a maintenance release), minor (increment for API additions). The way libtool does this is hard to follow and I need to look it up every time, so I'm not sure I can say changeset:r3906 is right. But if both autoconf and cmake builds get 1.8.2 that sounds ok. (Sorry, I can't test this today.)