Re: Patch review process

+1 on the idea of patch managers. As the patch managers should have good expertise on the specific fields, they are more productive on reviewing the patches and driving the development on the specific fields forward. ~Haohui On Mon, Feb 2, 2015 at 12:55 PM, Chris Nauroth wrote: > I like the ide

Re: Patch review process

I like the idea of patch managers monitoring specific queues of issues, perhaps implemented as a set of jira filters on different values for the component or label fields. Right now, looking at the whole HADOOP backlog is daunting. Using separate filtered review queues could help each reviewer fo

[jira] [Resolved] (HADOOP-11532) RAT checker complaining about PSD images

[ https://issues.apache.org/jira/browse/HADOOP-11532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved HADOOP-11532. - Resolution: Duplicate This is a duplicate of YARN-3113. > RAT checker complaining about PSD ima

Re: Patch review process

Many projects have unofficial "patch managers": http://producingoss.com/en/share-management.html#patch-manager People who go through outstanding issues, ensuring that each has reached a stable state, or at least a willing reviewer. -C On Mon, Feb 2, 2015 at 3:45 AM, Steve Loughran wrote: > > Gi

Re: Patch review process

Given experience of apache reviews, I don't know how much time to spend on it. I'm curious about Gerrit, but again, if JIRA integration is what is sought, Cruicible sounds better. Returning to other issues in the discussion 1. Improving test times would make a big difference; locally as well a

[jira] [Created] (HADOOP-11535) TableMapping related tests failed due to 'correct' resolving for test hostname

Kai Zheng created HADOOP-11535: -- Summary: TableMapping related tests failed due to 'correct' resolving for test hostname Key: HADOOP-11535 URL: https://issues.apache.org/jira/browse/HADOOP-11535 Project:

Build failed in Jenkins: Hadoop-Common-trunk #1394

See -- [...truncated 3865 lines...] Generating