You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-commits@hadoop.apache.org by Apache Wiki <wi...@apache.org> on 2012/03/19 07:31:07 UTC

[Hadoop Wiki] Update of "Roadmap" by Arun C Murthy

Dear Wiki user,

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

The "Roadmap" page has been changed by Arun C Murthy:
http://wiki.apache.org/hadoop/Roadmap?action=diff&rev1=17&rev2=18

  
  === Major Releases ===
  
- Major releases signify incompatible API changes.  Upgrading between major releases will generally require changes to user code.  We try to facillitate API upgrades by introducing new APIs in the prior major version, deprecating APIs that will be removed.  A major release primarily just removes APIs that were deprecated in the prior major release.  Thus, to upgrade to a new major release, one should update ones code so that it compiles without deprecation warnings in the final minor release of the prior major cycle.
+ Major releases signify incompatible API changes.  Upgrading between major releases will generally require changes to user code.  We try to facillitate API upgrades by introducing new APIs in the prior major version, deprecating APIs that will be removed.  
  
+ A major release primarily just removes APIs and features that were deprecated in the prior major release.  Thus, to upgrade to a new major release, one should update ones code so that it compiles without deprecation warnings in the final minor release of the prior major cycle.
+ 
+ Across all releases with the same ''major'' version, user-applications work without the need for 'any' change. Thus every release with the same ''major'' version is both API and 'on the wire' compatible.
+ 
- Major releases are made as needed, perhaps annually.
+ Major releases are made as needed, perhaps annually or even further apart.
  
  === Minor Releases ===
  
- Minor releases are made regularly, every few months.  Their APIs are back-compatible with prior minor releases, but might include new features, improvements and bug fixes.
+ Minor releases are made regularly, every few months.  Their APIs are back-compatible with prior minor releases, but might include new features, improvements and bug fixes. Also, across minor releases
+ 
+ Across all releases with the same ''major'' version, user-applications work without the need for 'any' change. Thus every release with the same ''major'' version is both API and 'on the wire' compatible.
  
  === Point Releases ===
  
  Point releases are made to fix critical bugs.  They do not introduce new features or make other improvements other than fixing bugs.  They are made on-demand.
+ 
+ Across all releases with the same ''major'' version, user-applications work without the need for 'any' change. Thus every release with the same ''major'' version is both API and 'on the wire' compatible.
  
  ''Note: The above rules do not apply until the 1.0 release.  Prior to 1.0, minor releases follow the rules for major releases, except they are still made every few months.''