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 MattFoley: http://wiki.apache.org/hadoop/Roadmap?action=diff&rev1=14&rev2=15 Comment: Added material from Arun Murthy's email of Wed, Aug 3, 2011 at 2:02 PM PDT, to common-dev, clarifying Sustaining Releases process 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 patch release that is intended for critical bug fixes. + 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 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. + + 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 ===
