IIRC, we also agreed that we didn't feel any compelling reason to make
a sweeping change to generics, but would likely just add them as we
see 'em, unless of course someone wants to do a wholesale patch. In
the case of generics, I see no reason why we can't intro them over
time, people using the non-generic forms will still work.
On Dec 12, 2008, at 7:44 AM, Grant Ingersoll wrote:
We agreed in the vote that we would allow generics, etc. in 3.0
including the removal of non-generic versions of the same methods.
In other words, we aren't strictly following the way we went from
1.9 to 2.0.
I sent a thread on 2.9/3.0 planning a while ago, but got no
responses...
On Dec 12, 2008, at 5:18 AM, Michael McCandless wrote:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
