We have been testing federation regularly with MapReduce with yahoo-merge branches. With trunk we missed the contrib (raid). The dependency with project splits has been crazy. Not sure how large changes can keep on top of all these things.
I am working on fixing the raid contrib. On Mon, May 2, 2011 at 2:44 PM, Todd Lipcon <t...@cloudera.com> wrote: > Apparently this merge wasn't tested against MapReduce trunk at all -- MR > trunk has been failing to compile for several days. Please see > MAPREDUCE-2465. I attempted to fix it myself but don't have enough > background in the new federation code or in RAID. > > -Todd > > On Thu, Apr 28, 2011 at 11:30 PM, Konstantin Shvachko > <shv.had...@gmail.com>wrote: > > > Thanks for clarifying, Owen. > > Should we have the bylaws somewhere on wiki? > > --Konstantin > > > > > > On Thu, Apr 28, 2011 at 1:33 PM, Owen O'Malley <omal...@apache.org> > wrote: > > > > > On Apr 27, 2011, at 10:12 PM, Konstantin Shvachko wrote: > > > > > > > The question is whether this is a > > > > * Code Change, > > > > which requires Lazy consensus of active committers or a > > > > * Adoption of New Codebase, > > > > which needs Lazy 2/3 majority of PMC members > > > > > > This is a code change, just like all of our jiras. The standard rules > of > > at > > > least one +1 on the jira and no -1's apply. > > > > > > Adoption of new codebase is adopting a new subproject or completely > > > replacing trunk. > > > > > > > Lazy consensus requires 3 binding +1 votes and no binding vetoes. > > > > > > This was clarified in the bylaws back in November. > > > > > > > > > > > > http://mail-archives.apache.org/mod_mbox/hadoop-general/201011.mbox/%3c159e99c4-b71c-437e-9640-aa24c50d6...@apache.org%3E > > > > > > Where it was modified to: > > > > > > Lazy consensus of active committers, but with a minimum of > > > one +1. The code can be committed after the first +1. > > > > > > -- Owen > > > > > > -- > Todd Lipcon > Software Engineer, Cloudera > -- Regards, Suresh
