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 EliCollins: http://wiki.apache.org/hadoop/Roadmap?action=diff&rev1=15&rev2=16 Comment: Updating out of date info Release planning is primarily coordinated through [[http://issues.apache.org/jira/browse/HADOOP|Hadoop's JIRA database]]. Use the "Roadmap" tab to see specific plans for upcoming releases. + For ideas about ''what'' you might contribute, please see the ProjectSuggestions and HowToContribute pages. - HdfsFutures provides a categorized list of features, some upcoming with their Jira links. - This is also a good place to go if you are searching for ideas for contributing to Hadoop's HDFS. == Release Numbering == @@ -37, +36 @@ For more details on how releases are created, see HowToRelease. - == Sustaining Release == + == Sustaining Releases == - The current sustaining branch is branch-0.20-security. It was branched from branch-0.20 with many features including security integrated in. + The current sustaining branch is branch-1. It was branched from branch-0.20 with many features including security integrated in. - Release Manager: Owen O'Malley + Because 0.21 had already been released, we added a new level to the release numbering. Thus version numbers on this branch look like 0.20.X.Y where X is > 200 and denotes the minor release from the branch. The Y denotes the point release that is intended for critical bug fixes to a previous sustaining release. The 0.205.0.1 release became the Hadoop 1.0.0 release, and we are now back to a three part (major.minor.point) version scheme. Changes for the next point releases of the sustaining branch need to be merged from branch-1 to branch-1.0 (or branch-1.1 etc). - Because 0.21 had already been released, we added a new level to the release numbering. Thus version numbers on this branch look like 0.20.X.Y where X is > 200 and denotes the minor release from the branch. The Y denotes the point release that is intended for critical bug fixes to a previous sustaining release. + See the [[http://hadoop.apache.org/common/releases.html|Hadoop Releases Page]] to see the full list of sustaining releases. Changes - The Release Manager for a sustaining release should announce the code freeze date as far in advance as possible, on the general list. Prior to that date, anyone interested in contributing to the release submits a patch to branch-0.20.security, and adds the sustaining release number to “Fix Version/s” in the Jira. Only functionality already committed to trunk should be submitted to a sustaining release. (The exception is if the functionality is not applicable to trunk.) The Release Manager is fully responsible for release content and timelines. + The Release Manager for a sustaining release should announce the code freeze date as far in advance as possible, on the general list. Prior to that date, anyone interested in contributing to the release submits a patch to branch-1, and adds the sustaining release number to “Target Version/s” in the Jira. Only functionality already committed to trunk should be submitted to a sustaining release. (The exception is if the functionality is not applicable to trunk.) The Release Manager is fully responsible for release content and timelines. After the code freeze date, the Release Manager will generate the release candidate and call a release vote in the usual way. After that point, only patches for issues rated “blocker” may be added to the release. - === 0.20.X.Y timeline === - - ==== 0.20.203 ==== - - First release off of 0.20-security and includes security and user limits. - - 0.20.203.0 was released on 2011/5/11. - - ==== 0.20.204 ==== - - Includes disk fail in place, where data nodes and task trackers stay up when drives fail. - - 0.20.204.0rc1 - currently under voting - - ==== 0.20.205 ==== - - 0.20.205 will branch in August 2011. - - ==== 0.20.206 ==== - - 0.20.206 will branch in October 2011. -
