+1 from me, too. Not because I have a vote or that I am for going to
1.5, but because it is inevitable and this is a well thought out,
fine plan. (excepting the aggressive timeline that has been hashed
out already in this thread)
I'd like to point out that there is a consequence of this plan and
how Lucene has done things in the past.
At 1.9 it was fully compatible with 1.4.3, with deprecations. 2.0
mostly had deprecations removed and a few bug fixes. Then the 2.x
series has been backwardly compatible but not with 1.x (except being
able to read prior indexes, perhaps a few other things.).
If we continue that same pattern, then there will be no 1.5 features
in 2.9. (Otherwise it won't compile under 1.4). Thus, 3.0 will have a
1.4.2 compatible interface. And except for new classes, new methods
and compile equivalent features (such as Enums), 1.5 features won't
appear in the 3.x series API.
I think it is very important to preserve the Lucene API where
possible and reasonable, not changing it without gain. Given that
this has been the practice, I don't think it is an issue.
-- DM Smith
On Jul 26, 2007, at 8:36 PM, Grant Ingersoll wrote:
I propose we take the following path for migrating Lucene Java to
JDK 1.5:
1. Put in any new deprecations we want, cleanups, etc.
2. Release 2.4 so all of Mike M's goodness is available to 1.4
users within the next 2-4 weeks using our new release mechanism
(i.e code freeze, branch, documentation. I tentatively volunteer
to be the RM, but hope someone will be my wingman on it).
3. Announce that 2.9 will be the last version under JDK 1.4
4. Put in any other deprecations that we want and do as we did when
moving from 1.4.3 to 1.9 by laying out a migration plan, etc.
5. Release 2.9 as the last official release on JDK 1.4
6. Switch 3.0-dev to be on JDK 1.5, removing any deprecated code
and updating ANT to use 1.5 for source and target.
7. Start accepting JDK 1.5 patches on 3.0-dev
If possible, efforts should be made to identify people who are
willing to backport 3.x changes to JDK 1.4 on 2.9 and give them
branch commit rights, but this is not a strict requirement of this
plan.
Thus:
+1 for JDK 1.5 as outlined in steps 1-7
0 if you don't care
-1 if you are against it
Since the weekend is coming up, how about we leave this vote open
until Monday?
You can see discussions of this here: http://www.gossamer-
threads.com/lists/lucene/java-dev/51421
Here is my +1.
Cheers,
Grant
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
