Release version 2.0

[dsmiley]

Version 2.0-SNAPSHOT has been used quite a bit at MITRE and has had some enhanced tests -- it's solid. The memory usage is better and it's more flexible to build/maintain indices since it's based directly off of Lucene instead of building a custom persisted memory structure, and it's simpler code too. The tagging performance wasn't specifically measured, but it was in aggregate with the rest of OpenSextant and there was no marked difference -- that's success as far as I'm concerned.

What 2.0 lacks as of this writing is v1.2's ability to use more rich text analysis, thanks to @westei. See #20. I'm a little conflicted on wether to just release it. I was about to announce that it'll happen anyway next week but I think this big feature mis-match and no truly pressing reason to release 2.0 quite yet so I should hold up, and document some remaining issues.

When 2.0 does get released, the master branch will be renamed to 1_x, and MemPF will become master.

[spacemansteve]

I need to run with Solr 4.8 but there are compatibility issues. Releasing the source would help me investigate these issues. Are there plans for 4.8 support? Is there a release schedule for the solr-text-tagger source?

[dsmiley]

I saw your email first and I replied that way, but for public posterity: Solr 4.8 isn't even out yet. I suspect that you've got a stale checkout since I added Solr 4.7 support a couple weeks ago and the particular API change you mentioned was affected by that. So it probably works in v4.8 but I haven't checked.

I'm still conflicted wether to release a 2.0 version that doesn't include a major feature from 1.x. I could put in the effort to port it; I was hoping @westei might but we've both been busy apparently.

[mubaldino]

FYI 4.8.0 is out now, as you know.

Does that help you gauge at all how to release 2.0 release? The snapshot of 2.0 has worked well enough, however if you have a timeline in mind, please let us know. Thanks, David.

[dsmiley]

I'm going to release 2.0 next week, moving into master branch position, and put the current master as a 1.x branch. 1.1 will remain a viable choice as it supports more flexible text analysis choices. I'll push 2.0 to Maven as well.

[mubaldino]

thanks, Dave. I published a 2.0-beta snapshot internally and have been using that copy to simplify things. java/SSL woes abound back here at the ranch. Regards, marc

[dsmiley]

I created a "v1x" branch off master, then deleted master. Then I renamed MemPF to master. You may have issues with your existing checkout, and this will explain it but it should be fixable. I'll push 2.0 in the morning.

[dsmiley]

I released 2.0. It should sync to Maven Central within 2 hours, if I recall.