1.3.0 release?
Closed this issue · 3 comments
@mwtoews with the release of libspatialindex 2.0.0, the current release of Rtree has tests that are broken (a version check). We should issue a new Rtree release.
Did you have any items you wanted to make sure were addressed or have any time to work some of the issues before we snapped off the release?
If there are no new features/API changes and only bug fixes, shouldn't it be 1.2.1?
shouldn't it be 1.2.1?
No strong opinion but given our release cadence being so slow, I thought a major version number would also align with prompting an update to libspatialindex since they are so closely linked.
Our wheel generation stuff would also need to be updated to do libspatialindex 2.0.0
Unfortunately, I have limited time to address new features / resolve issues with Rtree. However, I can find some time this week to update the wheel generation for libspatialindex 2.0.0 and push out a new release.
As for the next logical version, I don't have any strong opinions. Since libspatialindex headers are included with binary wheels, probably a minor increment to 1.3.0 makes most sense.