Re: Which newbie Jira's need work?

If you happen to know which committers tend to do a lot of code reviews in the specific area of the code covered by your patch, then tagging them in a jira comment is an effective approach. If you're unsure who to contact, then please feel free to email the appropriate project-specific *-dev list

Re: IMPORTANT: testing patches for branches

1. I really like the new patch process, especially the at-a-glance summary 2. I think being -1 on whitespace is overkill; Its just part of my git apply -p 0 -3 --verbose --whitespace=fix action. Accordingly, I won't reject patches on whitespace alone. 3. if checkstyle is complaining, how to

2.7.1 status

As we talked before [1], I am going to start the push for 2.7.1 [2]. Here are the things I am going to do, with help from others in the community - Review current 2.7.1 content to make sure only bug fixes went in - Review 2.8 to see if any important bug fixes didn't get merged into 2.7.1 -

Re: IMPORTANT: testing patches for branches

About (3.) , a lot of the check style rules seem to be arcane/unnecessary. Please see : https://issues.apache.org/jira/browse/HADOOP-11869 On Thu, Apr 23, 2015 at 10:45 AM, Steve Loughran ste...@hortonworks.com wrote: 1. I really like the new patch process, especially the at-a-glance summary

[jira] [Created] (HADOOP-11874) s3a can throw spurious IOEs on close()

Steve Loughran created HADOOP-11874: --- Summary: s3a can throw spurious IOEs on close() Key: HADOOP-11874 URL: https://issues.apache.org/jira/browse/HADOOP-11874 Project: Hadoop Common Issue

[jira] [Resolved] (HADOOP-11851) s3n to swallow IOEs on inner stream close

[ https://issues.apache.org/jira/browse/HADOOP-11851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-11851. - Resolution: Fixed Fix Version/s: 2.7.1 s3n to swallow IOEs on inner stream

[jira] [Created] (HADOOP-11872) hadoop dfs command prints message about using yarn jar on Windows(branch-2 only)

Varun Vasudev created HADOOP-11872: -- Summary: hadoop dfs command prints message about using yarn jar on Windows(branch-2 only) Key: HADOOP-11872 URL: https://issues.apache.org/jira/browse/HADOOP-11872

Re: Which newbie Jira's need work?

Hi Tsuyoshi On Wed, Apr 22, 2015 at 9:16 AM, Tsuyoshi Ozawa oz...@apache.org wrote: Hi Darrell, Thank you for having interest for contributions to Hadoop project! * How do I know if a newbie Jira is even still valid? Please ping committers whether the issue is valid when the issue looks

Jenkins build is back to normal : Hadoop-common-trunk-Java8 #174

See https://builds.apache.org/job/Hadoop-common-trunk-Java8/174/changes

Re: IMPORTANT: testing patches for branches

On Apr 22, 2015, at 11:34 PM, Zheng, Kai kai.zh...@intel.com wrote: Hi Allen, This sounds great. Naming a patch foo-HDFS-7285.00.patch should get tested on the HDFS-7285 branch. Does it happen locally in developer's machine when running test-patch.sh, or also mean something in

RE: IMPORTANT: testing patches for branches

Overall approach and summary is very good... well done Apart from steve pointed which I had also noticed, following one also i had seen where I did not seen any clue.. The patch artifact directory on has been removed! This is a fatal error for test-patch.sh. Aborting. Jenkins (node H8)