@hadoop.apache.org; mapreduce-...@hadoop.apache.org;
yarn-...@hadoop.apache.org
Subject: Re: IMPORTANT: testing patches for branches
On Apr 22, 2015, at 11:34 PM, Zheng, Kai wrote:
> Hi Allen,
>
> This sounds great.
>
>>> Naming a patch foo-HDFS-7285.00.patch should get te
On Apr 22, 2015, at 11:34 PM, Zheng, Kai 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 Hadoop Jen
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 Hadoop Jenkins building when a JIRA becoming patch
available? Thanks.
Regard
Oh, this is also in the release notes, but one can use a git reference # as
well. :) (with kudos to OOM for the idea.)
On Apr 22, 2015, at 8:57 PM, Allen Wittenauer wrote:
>
> More than likely. It probably needs more testing (esp under Jenkins).
>
> It should be noted that the code in test
More than likely. It probably needs more testing (esp under Jenkins).
It should be noted that the code in test-patch.sh has lots of problems with
branch-0, minor, and micro releases. But for major releases, it seems to work
well for me. :)
On Apr 22, 2015, at 8:45 PM, Vinod Kumar Vavilapa
Does this mean HADOOP-7435 is no longer needed / closeable as dup?
Thanks
+Vinod
On Apr 22, 2015, at 12:34 PM, Allen Wittenauer wrote:
>
> Hey gang,
>
> Just so everyone is aware, if you are working on a patch for either a
> feature branch or a major branch, if you name the patc
