lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven A Rowe <>
Subject RE: Proposal for changing Lucene's backwards-compatibility policy
Date Fri, 16 Oct 2009 17:27:27 GMT
On 10/16/2009 at 2:58 AM, Michael Busch wrote:
> B) best effort drop-in back compatibility for the next minor version
> number only, and deprecations may be removed after one minor release
> (e.g. v3.3 will be compat with v3.2, but not v3.4)

This is only true on a per-feature basis.  For example, if feature A is deprecated in v3.1,
and feature B is deprecated in v3.2, then v3.3 will be "compat" with v3.2 only as far as feature
B is concerned; feature A will no longer be present in v3.3.

Under these circumstances, saying "v3.3 will be compat with v3.2" with no caveats sounds to
me like false advertising.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message