I’m fine with calling it 1.7.0.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Principal Data Scientist, Engineering Administrative Office (3010) Manager, Open Source Projects Formulation and Development Office (8212) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 180-503E, Mailstop: 180-502 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Director, Information Retrieval and Data Science Group (IRDS) Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA WWW: http://irds.usc.edu/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ On 11/7/16, 9:59 AM, "Joern Kottmann" <[email protected]> wrote: Hello all, since our last release it has been a while and we received quite a few changes which would be nice to get released. There are still some open Jira issues, but mostly smaller things that can be wrapped up rather quickly. Is there anything important missing which should go into the next release? Otherwise I think we should also aim for more frequent released and just make one again early next year, with all the stuff we might miss out now. We took in a patch - as part of OPENNLP-830 - to replace our self-made hash table with the java.util.HashMap. This change is not backward compatible for folks who extend AbstractModel. Should we go with 1.6.1 as a next version or should we make 1.7.0 to reflect that? Previously we only had backward incompatible changes in versions which bumped by the second number. Maybe that is better choice. It will probably break some peoples code when they update. We also have lots of deprecated API still in OpenNLP, should we try to remove as much as possible of it now? Jörn
