Michael Busch wrote:
I think we should change the backwards-compatibility policy as
proposed in LUCENE-1698 and remove some deprecated things (inlcuding
the old TokenStream API, maybe query parser) in 3.1, not 3.0.
I don't think we should have a 2.5 release - this clearly shows the
disadvantages of our current bw-policy.
Michael
I think the only advantage to that policy is to save major number space
(it will take us longer to get to Lucene 10) - and the disadvantages are
laid out in the comments.
If we find we have a lot we need to remove after 3.0, jumping to Lucene
4 makes the most sense to me.
I still like the idea of at least *attempting* back compat between major
versions - its much more intuitive than the every other minor stuff.
--
- Mark
http://www.lucidimagination.com
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
