lucene-java-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Lucene-java Wiki] Update of "BackwardsCompatibility" by MarkMiller
Date Sun, 11 Apr 2010 15:10:40 GMT
Dear Wiki user,

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

The "BackwardsCompatibility" page has been changed by MarkMiller.
http://wiki.apache.org/lucene-java/BackwardsCompatibility?action=diff&rev1=8&rev2=9

--------------------------------------------------

  
  == APIs and Compilation ==
  
- Minor versions should always have complete back-compatiblity for supported (i.e. public
and protected) APIs.  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, as long as only supported APIs are used.
+ Minor versions should always have complete back-compatiblity for supported (i.e. public
and protected) APIs.  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, as long as only supported APIs are used. This is no longer the case
though - back compat breaks have become more and more common over time, and you will need
to refer to the "Changes in backwards compatibility policy" section of CHANGES to see all
of the breaks between minor 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'''.
+ A major release may also 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'''.
  
  Package-private APIs (e.g. methods without any modifier such as public or protected) are
not supported and thus exempt from these back-compatibility requirements. They can change
without warning or intermediate deprecation.
  

Mime
View raw message