On Tue, Aug 2, 2011 at 12:25 PM, Eli Collins <e...@cloudera.com> wrote: > On Tue, Aug 2, 2011 at 12:19 PM, <milind.bhandar...@emc.com> wrote: >> Having talked to various folks in the community about their willingness to >> stabilize and use 0.22 and make it production-quality, here is what I >> propose: >> >> 1. Cut a release 0.22.0 without mapreduce-2178 patch, with >> hadoop.security.authentication set to simple (I.e. No authentication). >> Make sure that MR-2178 is highlighted as known-issue in the top-level dir >> (create a KNOWN-ISSUES.txt ?), and carry out a vote. >> >> 2. Later, when MR-2178 patch is committed, cut a release for 0.22.1. (I >> have heard of folks working on it, but no date commitments yet.) >> >> The reason a 0.22.0 release should happen, IMHO, even without MR-2178, is >> that the other components of Hadoop stack (e.g. Pig, hbase, hive etc) will >> have a release to test against, and fix any issues for incompatibility. >> Also, for folks who do not use kerberos authentication (>90% of the hadoop >> users, to my knowledge), it will be a release closest to trunk, with HDFS >> appends. Plus, any issues found in the HDFS part of the release would be >> directly applicable to the trunk and other future releases. (Not so about >> map-reduce, which will undergo major surgery in trunk because of MR-279.) >> >> Thoughts ? >> > > Sounds reasonable to me. #1 is what we did for the 0.21 release.
Actually, I didn't read close enough. For 0.21 we actually removed the task tracker, think it makes sense to do that here as well. Thanks, Eli
