You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-commits@lucene.apache.org by Apache Wiki <wi...@apache.org> on 2009/01/26 14:37:40 UTC

[Lucene-java Wiki] Update of "BackwardsCompatibility" by MikeMcCandless

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lucene-java Wiki" for change notification.

The following page has been changed by MikeMcCandless:
http://wiki.apache.org/lucene-java/BackwardsCompatibility

The comment on the change is:
Adding jar-drop-in back compat between minor releases

------------------------------------------------------------------------------
  
  == APIs and Compilation ==
  
- Minor versions should always have complete API back-compatiblity.  That's to say, any code developed against '''X.0''' should continue to run without alteration against all '''X.N''' releases.  
+ Minor versions should always have complete API back-compatiblity.  That's to say, any code developed against '''X.0''' should continue to run without alteration and without recompilation (ie, simply drop in the new JAR) against all '''X.N''' releases.  
  
  A major release may introduce incompatible API changes.  The transition strategy is to introduce new APIs in release '''X.N''', deprecating old APIs, then remove all deprecated APIs in release '''X+1.0'''.