lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Earwin Burrfoot <ear...@gmail.com>
Subject deprecating Versions
Date Sat, 27 Nov 2010 20:44:54 GMT
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.

-- 
Kirill Zakharenko/Кирилл Захаренко (earwin@gmail.com)
Phone: +7 (495) 683-567-4
ICQ: 104465785

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


Mime
View raw message