Where would JIRA fit into the PR workflow? Would we file JIRAs just to
track github PRs and have all of the discussion on the PR?
Eric
On Mon, Jul 22, 2019 at 1:10 PM Dinesh Chitlangia
wrote:
> +1 Absolutely. It also makes it easy/clean for reviewers to leave specific
> comments and the
+1 Absolutely. It also makes it easy/clean for reviewers to leave specific
comments and the authors can make incremental changes without the hassles
of generating iterative patch files.
Thanks,
Dinesh
On Mon, Jul 22, 2019 at 2:06 PM Wei-Chiu Chuang wrote:
> Historically, Hadoop developers
Historically, Hadoop developers create patches and attache them to JIRA,
andthen the Yetus bot runs precommit against the patch in the JIRA.
The Github PR is more convenient for code review and less hassle for
committers to merge a commit. I am proposing for the community to prefer
Github PR over
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1205/
No changes
-1 overall
The following subsystems voted -1:
asflicense findbugs hadolint pathlen unit xml
The following subsystems voted -1 but
were configured to be filtered/ignored:
cc
For more details, see
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/390/
No changes
-1 overall
The following subsystems voted -1:
asflicense findbugs hadolint pathlen unit xml
The following subsystems voted -1 but
were configured to be filtered/ignored:
cc
@adam.antal
The submarine development team has completed the following preparations:
1. Established a temporary test repository on Github.
2. Change the package name of hadoop submarine from org.hadoop.submarine to
org.submarine
3. Combine the Linkedin/TonY code into the Hadoop submarine module;
Thanks for all the positive feedback,
I opened INFRA-18777 to request the proposed change.
Marton
On 7/18/19 10:02 AM, Masatake Iwasaki wrote:
> +1
>
> Thanks,
> Masatake Iwasaki
>
> On 7/17/19 15:07, Elek, Marton wrote:
>> Hi,
>>
>> Github UI (ui!) helps to merge Pull Requests to the
