On Wed, Feb 15, 2012 at 6:36 AM, Shai Erera wrote:
> It makes sense to me, but it also means that 4.0 will go out with deprecated
> API that will exist until 5.0 is out.
>
> I only raised it to learn if this was done by mistake, or there is some
> logic behind it. I guess that for me, reading MIGR
>
> In general I think if we can add transition mechanisms like this to
> make it easier for people to cut over, we should are there reasons
> we should not do this?
>
> On Wed, Feb 15, 2012 at 1:59 AM, Shai Erera wrote:
> > Hi
> >
> >
Feb 15, 2012 at 1:59 AM, Shai Erera wrote:
> Hi
>
> Why do we have deprecated methods on trunk (e.g. IndexReader.open())?
> Shouldn't they be deleted?
>
> Shai
--
lucidimagination.com
-
To unsubscribe, e-
taphi.de
>
> eMail: u...@thetaphi.de
>
> ** **
>
> *From:* Shai Erera [mailto:ser...@gmail.com]
> *Sent:* Wednesday, February 15, 2012 8:00 AM
> *To:* dev@lucene.apache.org
> *Subject:* Deprecated methods on trunk
>
> ** **
>
> Hi
>
> Why do we have deprecated methods on trunk (e.g. IndexReader.open())?
> Shouldn't they be deleted?
>
> Shai
>
From: Shai Erera [mailto:ser...@gmail.com]
Sent: Wednesday, February 15, 2012 8:00 AM
To: dev@lucene.apache.org
Subject: Deprecated methods on trunk
Hi
Why do we have deprecated methods on trunk (e.g. IndexReader.open())?
Shouldn't they be deleted?
Shai
Hi
Why do we have deprecated methods on trunk (e.g. IndexReader.open())?
Shouldn't they be deleted?
Shai
