Hey Owen, I took a quick look at the changes in the branch (specifically the range of 200 or so changes where the first line of the commit doesn't reference a jira). Most of these look like backports of patches on jira, however there also seem to be changes that don't correspond to changes in trunk or patches on jiras. Some of these introduce new configuration options (eg hadoop.security.uid.cache.secs) or public classes (eg QueueProcessingStatistics) that don't exist in trunk.
How do we ensure future releases won't violate compatibility with respect to this release? Do we plan to have jiras with patches against trunk for these changes, at least for the set of changes that affect public APIs? If so, should that come first? Thanks, Eli On Fri, Apr 29, 2011 at 4:09 PM, Owen O'Malley <omal...@apache.org> wrote: > I think everything is ready to go on the 0.20.203.0 release. It includes > security and a lot of improvements in the capacity scheduler and JobTracker. > > Should we release http://people.apache.org/~omalley/hadoop-0.20.203.0-rc0/? > > -- Owen
