lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael McCandless <luc...@mikemccandless.com>
Subject Re: deprecating Versions
Date Tue, 30 Nov 2010 11:10:33 GMT
On Sat, Nov 27, 2010 at 3:44 PM, Earwin Burrfoot <earwin@gmail.com> wrote:
> I think we should deprecate and remove Version constants as Lucene progresses?
>
> Imagine there's a number of features in 4.x that get deprecated and
> un-defaulted in 5.x, then removed in 6.x
> Our user compiled with Version.4_0, it was cool in 4.x, then it still
> worked in 5.x, as we preserved index compatibility, then it silently
> broke in 5.x -> not good.
> If we deprecated Version.4_0 @ 5.x, he'd get a warning if he tried
> recompiling. Then if we removed Version.4_0 @ 6.x, his app won't start
> anymore, even without recompiling -> failfast.
>
> Going with this, we should deprecate 3x in trunk and delete 2x. In 3x
> branch, we should deprecate 2x.

+1, this makes complete sense.

Ie it simply "matches" our index back compat policy, which is the
intention of when these version constants should be used.

Mike

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message