On Mon, 24 Aug 2009, Tim Smith wrote:
Here's my vote on the topic of 2.9 vs 3.0
Next release should be 2.9
This release provides TONs of new APIs for things like Hit Collection,
Scoring, Sorting, etc
If all the deprecated stuff were removed for the "next" release, this would
be impossible for any application developer to consume (unless they are
using very light high level use of lucene APIs)
I would then vote for a very fast turnaround on 3.0
deprecations removed, generics added, performance improvements possible with
java 1.5, but no major new features
I would argue that small features should be allowed in (provided they would
not cause any postponement to 3.0 going out soon)
This allows me (as a application developer) to do the following:
upgrade to 2.9 (port my code to use all the new APIs)
hopefully, once i have fully ported everything to 2.9, 3.0 will now be ready
(or will be soon)
then, i can drop in 3.0 (very minor porting required here) and all the
deprecated APIs with their slowing "wrapper" code for back-compat will now
be gone, along with improvements in using StringBuilder instead of
StringBuffer, generics, and other performance improvements.
I would hope to never release any of my code running 2.9 and instead release
with 3.0, however as a app developer, i need 2.9 as a bridge for porting
+1
I'd add that 3.0 should also contain 2.9 bug fixes over new features.
Consider 3.0 a 2.9.1 bug fix release with deprecations removed and Java 1.5
goodness :)
Andi..
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
