Geometry v1.2.2 release

[randallwhitman]

Are there specific plans for a v1.2.2 release? I would like to release v1.2 of spatial-framework-for-hadoop after the current GeoJSON enhancements are merged. If it makes sense, I may coordinate that with Geometry v1.2.2 release.

@climbage @alocke @stolstov

[stolstov]

I am looking into an issue in the Buffer operation we found locally (buffer may be slightly larger than it should on concave corners). I'd like it to go into 1.2.2.

[randallwhitman]

Do you have a target timeframe?
With recently filed Esri/gis-tools-for-hadoop#43 , once we release Spatial-Framework-for-Hadoop v1.2 , people won't hit that exception any more with release JARs.

[randallwhitman]

@alocke @climbage @stolstov Do we have a checklist or howto on making a numbered release for Geometry API? The spatial-framework-for-hadoop release JAR files are rather behind master - need to make a release of spatial-framework whether or not coordinated with Geometry.

[stolstov]

@climbage made previous releases for spatial-framework-for-hadoop. We don't make numbered releases otherwise.

[randallwhitman]

Just today I made note that there is an interface change - namely a change in exceptions thrown by OGCGeometry fromJson and fromGeoJson. Does this mean that instead of 1.2.2 we need to bump the version number to 1.3 or even 2.0 ?

[kjkrum]

I don't know if this project has documented its versioning strategy. Under Semantic Versioning, this would indeed make it version 2.0. (Or the change should be saved for 2.0.)

In any case, throwing Exception is not very useful to the client, and is perceived as sloppy or lazy.

[stolstov]

If I remember correctly the change was to remove dependency on 3rd party libraries from the interface. We'll need to remove this dependency eventually.

[stolstov]

@randallwhitman @alocke We need a final testing round.

[randallwhitman]

If I remember correctly the change was to remove dependency on 3rd party libraries from the interface.

In other words, to decouple interface versus implementation.

We'll need to remove this dependency eventually.

With a version number at which we can make interface change, I guess.