You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jclouds.apache.org by Apache Wiki <wi...@apache.org> on 2014/07/01 02:39:03 UTC

[Jclouds Wiki] Update of "DeprecationAndBetaPolicy" by AndrewPhillips

Dear Wiki user,

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

The "DeprecationAndBetaPolicy" page has been changed by AndrewPhillips:
https://wiki.apache.org/jclouds/DeprecationAndBetaPolicy?action=diff&rev1=3&rev2=4

  
  === Deprecation ===
  
- jclouds avoids backwards-incompatible changes between minor versions (e.g. from MAJOR.x to MAJOR.x) unless exceptional circumstances arise, e.g. critical security issues. Changes that are not backwards compatible should be approached as follows:
+ jclouds avoids backwards-incompatible changes between minor versions (e.g. from MAJOR.x to MAJOR.y) unless exceptional circumstances arise, e.g. critical security issues. Changes that are not backwards compatible should be approached as follows:
  
   1. Deprecation of code and removal of deprecated code will only happen on major releases (e.g. MAJOR.0)
-  1. The new methods, classes, etc. are committed to master and the latest release branch (branch MAJOR.0)
+  1. The new methods, classes, etc. are committed to master and the latest release branch (branch MAJOR.x)
   1. The old methods, classes, etc. that are to be removed are marked as {{{@Deprecated}}} (with an annotation and a Javadoc tag) on the latest release branch. The Javadoc should explain:
    1. in which release (typically, the next major version, MAJOR+1.0) the deprecated method, class, etc. will be removed
    1. which alternative(s) to use