Releasing NTS 2.6.0 #739
airbreather
started this conversation in
General
Replies: 1 comment
-
@airbreather, in general I have no objections to drive a different release schedule than JTS. In this particular situation though, I think we should wait for the next JTS release, since that is due. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Some folks from across my company have pinged me about the coverage tools that have been ported to NTS since the 2.5.0 release, very enthusiastic to get their hands on this stuff since this has been a pain point at our company for decades.
My immediate response was to point out that NTS stable releases almost always track JTS stable releases: since there has been no stable JTS release with these APIs, then it would be a bit of a risk to jump the gun on this, since we could no longer easily adopt breaking changes that JTS might easily make between now and when the APIs land in a stable release.
However, the more I explore it, the less satisfied I am with that answer. Here's a timeline:
To sum that up, the new polygon coverage APIs have been available to very early adopters for almost as long as stable-channel users have had JTS 1.19, and more generally to GEOS users (without a "beta" tag) for like 8 months now.
@FObermaier I'm curious what you might think about a 2.6.0 release? If you want to see JTS stabilize first, then I will support that decision entirely, but I think it would still be nice to at least publish a 2.6.0 prerelease on NuGet to make it easier for more early adopters to get their hands on this.
I've been involved in some internal projects at my company where it made more sense to use NTS 2.6.0 from the prerelease feed than any alternative at hand, and I am quite happy with that decision, even after seeing a couple of questionable-looking outputs from the coverage validator that I have been procrastinating to do the work to isolate and report (just two weird corner cases, pun intended, that look unrealistic but not definitely obviously illegal).
Beta Was this translation helpful? Give feedback.
All reactions