OK, I think all the binding votes are for adopting JDK 1.5 with the
following plan:
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 months or so (no hard date) using our new release
mechanism (i.e
H ... just a nit (or did I miss something?) in (2), do you mean 2.3?
-Original Message-
From: Grant Ingersoll [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 02, 2007 5:29 AM
To: java-dev@lucene.apache.org
Subject: Re: [VOTE] Migrate Lucene to JDK 1.5 for 3.0 release
OK, I think
@lucene.apache.org
Subject: Re: [VOTE] Migrate Lucene to JDK 1.5 for 3.0 release
OK, I think all the binding votes are for adopting JDK 1.5 with the
following plan:
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 months
+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
On Jul 30, 2007, at 8:18 AM, DM Smith wrote:
+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
27 jul 2007 kl. 02.36 skrev Grant Ingersoll:
I propose we take the following path for migrating Lucene Java to
JDK 1.5:
+1
Curiosa, the only requirement I've had for 1.4 lately is when I've
been fooling around running Lucene on my router. A small embedded
Linux (OpenWRT) and I've
+1, and 2 months for 2.4 sounds good (side note: do a Solr release right after
that?)
Otis
- Original Message
From: Grant Ingersoll [EMAIL PROTECTED]
To: java-dev@lucene.apache.org
Sent: Friday, July 27, 2007 2:36:39 AM
Subject: [VOTE] Migrate Lucene to JDK 1.5 for 3.0 release
I
+1 on moving to JDK 1.5
I'm also psyched for more frequent releases! But in this case I would
like to get both the Analyzer optimizations (re-using tokens) and
LUCENE-845 in before 2.3 if I can. 2 months should be a good time
frame for that.
Mike
Grant Ingersoll [EMAIL PROTECTED] wrote:
Here is my +1.
not sure if Solr committers votes count or if it just the PMC, but +1
-Mike
Likewise, my +1
--
View this message in context:
http://www.nabble.com/-VOTE--Migrate-Lucene-to-JDK-1.5-for-3.0-release-tf4154899.html#a11833799
Sent from the Lucene - Java Developer mailing
On Jul 26, 2007, at 8:56 PM, Michael Busch wrote:
Grant Ingersoll wrote:
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
Hi Grant,
2-4 weeks seems quite soon considering that 2.2 is very new and that
Grant Ingersoll wrote:
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
Hi Grant,
2-4 weeks seems quite soon considering that 2.2 is very new and that
there are a lot of open issues targeted for 2.3. For
On 26-Jul-07, at 5: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
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,
13 matches
Mail list logo
