hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nigel Daley <nda...@mac.com>
Subject Re: [VOTE] Should we define the Common committers as HDFS + MapReduce committers?
Date Mon, 16 Aug 2010 23:51:03 GMT
Doug, I don't think that's what this vote is doing.  It's not giving all committers access
to HDFS + MR + Common.  It seems to be just making committers for Common the union of HDFS
and MR.

I'm +1 on the vote.

Nige

On Aug 16, 2010, at 3:37 PM, Doug Cutting wrote:

> +1 I believe that so long as we have synchronized releases then we're co-developing a
single product and should be a single community.
> 
> Doug
> 
> On 08/16/2010 02:38 PM, Owen O'Malley wrote:
>> Since the project split, it is mostly required that any MapReduce or
>> HDFS committers have access to change Common. We haven't had any cases
>> where we wanted to nominate any one for just Common. Toward the goal of
>> simplifying the structure, I'd propose that we define the Common
>> committers as precisely the union of the HDFS committers and MapReduce
>> committers.
>> 
>> Clearly, I'm +1.
>> 
>> -- Owen


Mime
View raw message