Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <9ac0c6aa0812120218u42f5ffd1we938a1b4d04fb9fc@mail.gmail.com>
Date: Fri, 12 Dec 2008 05:18:56 -0500
From: "Michael McCandless" <lucene@mikemccandless.com>
To: java-dev@lucene.apache.org
Subject: 2.9/3.0 plan & Java 1.5
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_5261_31543213.1229077136063"

------=_Part_5261_31543213.1229077136063
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Taking this to java-dev (off Jira)...

Mark Miller (Jira) wrote:

> I thought there were some that wanted to change some of the API to java
> 5 for the 3.0 release, cause I thought back compat was less restricted
> 2-3. I guess mabye that won't end up happening, if it was going to, it
> seems we'd want to deprecate what will be changed in 2.9.

I could easily be confused on this... but I thought 3.0 is the first
release that's allowed to include Java 1.5 only APIs (eg generics).

Meaning, we could in theory intro APIs with generics with 3.0,
deprecating the non-generics versions, and then 4.0 (sounds insanely
far away!) would be the first release that could remove the deprecated
non-generics versions?

That said, I think the "plan" is to release 2.9 soonish (early next
year?), and then fairly quickly turnaround a 3.0 that doesn't have too
many changes except the removal of the deprecated (in 2.9) APIs.  Ie
in practice it won't be until 3.1 when we would intro new
(generics-based) APIs.

Mike

------=_Part_5261_31543213.1229077136063
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<br>Taking this to java-dev (off Jira)...<br><br>Mark Miller (Jira) wrote:<br><br>&gt; I thought there were some that wanted to change some of the API to java <br>&gt; 5 for the 3.0 release, cause I thought back compat was less restricted <br>
&gt; 2-3. I guess mabye that won&#39;t end up happening, if it was going to, it <br>&gt; seems we&#39;d want to deprecate what will be changed in 2.9.<br><br>I could easily be confused on this... but I thought 3.0 is the first<br>
release that&#39;s allowed to include Java 1.5 only APIs (eg generics).<br><br>Meaning, we could in theory intro APIs with generics with 3.0,<br>deprecating the non-generics versions, and then 4.0 (sounds insanely<br>far away!) would be the first release that could remove the deprecated<br>
non-generics versions?<br><br>That said, I think the &quot;plan&quot; is to release 2.9 soonish (early next<br>year?), and then fairly quickly turnaround a 3.0 that doesn&#39;t have too<br>many changes except the removal of the deprecated (in 2.9) APIs.&nbsp; Ie<br>
in practice it won&#39;t be until 3.1 when we would intro new<br>(generics-based) APIs.<br><br>Mike<br>

------=_Part_5261_31543213.1229077136063--