hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Jue <teamp...@gmail.com>
Subject Re: [VOTE] Should we define the Common committers as HDFS + MapReduce committers?
Date Tue, 17 Aug 2010 17:41:42 GMT
+1

On Tue, Aug 17, 2010 at 1:28 PM, Tsz Wo (Nicholas), Sze
<s29752-hadoopgeneral@yahoo.com> wrote:
> It is possibly to have contributors who are only interested in RPC,
> serialization, compression, etc.  However, just as Owen mentioned, we don't have
> such cases yet.  We might decide how to accommodate these contributors when we
> have such cases.
>
> +1
>
> Nicholas
>
>
>
>
> ----- Original Message ----
>> From: Owen O'Malley <omalley@apache.org>
>> To: general@hadoop.apache.org
>> Sent: Mon, August 16, 2010 2:38:53 PM
>> Subject: [VOTE] Should we define the Common committers as HDFS + MapReduce
>>committers?
>>
>> 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