I'm fine with either solution, but my preference would be to remove all
deprecated stuff and release version 2.0.
Am 20.02.2019 um 08:42 schrieb Bruno P. Kinoshita:
Hi all,
Just finished merging a pull request to TEXT-104, where the JaroWinkler
distance was updated. The class was actually computing a text similarity score,
not an edit distance. The user that contributed did a great job moving the
logic into a separate class, then updating the method to return a distance
instead.
Later I realized this would break both behaviour and binary compatibility.
So just wondering what others think. Is it time to gather a few more issues in
text, maybe even consider updating libraries/java/etc, drop @Deprecated stuff,
and prepare a 2.0? Or is it too soon, and instead revert moving the code to a
branch, and update TEXT-104 with a note about the branch?
CheersBruno
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
