Folks, we have 53 patches that are in the "Patch Available" state.  
This is an unhealthy situation.

Can committers please be more aggressive at reviewing patches and  
kicking them out of this state if the patches aren't ready?

Thanks,
Nige
Hadoop Release Manager

I'm going to try to make some time to review and commit a few patches
this coming week.
However, I did notice that a lot of the available patches are related to
Chukwa. I'm not very familiar with that code base or the project in general.
Is the ultimate goal to split that out into a Hadoop sub project much
like Hive and HBase? It seems like it's being very actively developed
on, splitting it out would reduce the Hadoop patch load as well as jira
traffic a lot.

/Johan

Nigel Daley wrote:
> Folks, we have 53 patches that are in the "Patch Available" state.  
> This is an unhealthy situation.
>
> Can committers please be more aggressive at reviewing patches and
> kicking them out of this state if the patches aren't ready?
>
> Thanks,
> Nige
> Hadoop Release Manager

+1 to splitting Chukwa out as a subproject.

On Sat, Feb 7, 2009 at 2:53 PM, Johan Oskarsson <[EMAIL PROTECTED]> wrote:

> I'm going to try to make some time to review and commit a few patches this
> coming week.
> However, I did notice that a lot of the available patches are related to
> Chukwa. I'm not very familiar with that code base or the project in general.
> Is the ultimate goal to split that out into a Hadoop sub project much like
> Hive and HBase? It seems like it's being very actively developed on,
> splitting it out would reduce the Hadoop patch load as well as jira traffic
> a lot.
>
> /Johan
>
>
> Nigel Daley wrote:
>
>> Folks, we have 53 patches that are in the "Patch Available" state.  This
>> is an unhealthy situation.
>>
>> Can committers please be more aggressive at reviewing patches and kicking
>> them out of this state if the patches aren't ready?
>>
>> Thanks,
>> Nige
>> Hadoop Release Manager
>>
>
>