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

See

Re: Branch policy question

It sounds like the community doesn't have a consistent point of view on the policy. Setting aside policy for a moment, I've always considered a few different branching models available when I start coding something big, with each model offering different features. 1. Apache mainline branches:

Re: Branch policy question

> On 3/22/16, 11:03 PM, "Allen Wittenauer" > wrote: > > >> On Mar 22, 2016, at 6:46 PM, Gangumalla, Uma > >>wrote: > >> > >>> is it possible for me to setup a branch, self review+commit to that > >>> branch, then request a branch

Jenkins build is back to normal : Hadoop-Common-trunk #2525

See

Re: Branch policy question

> On 22 Mar 2016, at 18:23, Andrew Wang wrote: > > A branch sounds fine, but how are we going to get 3 +1's to merge it? If > it's hard to find one reviewer, seems even harder to find two. Given that only one +1 is needed to merge a non-branch patch, he could in

[jira] [Resolved] (HADOOP-12857) Rework hadoop-tools

[ https://issues.apache.org/jira/browse/HADOOP-12857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-12857. --- Resolution: Fixed Fix Version/s: 3.0.0 Thanks for the review! Committed to

Re: Branch policy question

A feature branch seems reasonable for this work: multiple reviewable patches that are meaningful only after all of them get in. I guess most comments here that had concerns for a branch were primarily based on the initial reasoning of not being able to find a reviewer. Coming to RTC and CTR, I

Re: Branch policy question

> On 22 Mar 2016, at 16:14, Allen Wittenauer wrote: > > > Since it’s nearly impossible for me to get timely reviews for some > build and script changes, is it possible for me to setup a branch, self > review+commit to that branch, then request a branch merge? I’m

Re: Branch policy question

I think this is good technical justification for commit-then-review in a feature branch, and I would be +1 to support it. Just to briefly summarize one of my earlier comments, I see this as a way to unblock solo development work and keep it moving in parallel while rallying community members for

Re: Branch policy question

> On Mar 23, 2016, at 10:25 AM, Chris Nauroth wrote: > > 2. Apache feature branches: Sign-off may come from designated branch > committers in addition to full committers. It's OK to break the branch > for work in progress, but it must be fixed before a merge. It's

[jira] [Resolved] (HADOOP-12721) Hadoop-tools jars should be included in the classpath of hadoop command

[ https://issues.apache.org/jira/browse/HADOOP-12721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-12721. --- Resolution: Won't Fix HADOOP-12857 should have effectively fixed this issue for

Re: Branch policy question

It's interesting to go back to the change in bylaws in 2011 that introduced the requirement for 3 binding +1s on a branch merge [1]. The text of that resolution suggests that it's supportive of commit-then-review if that's what the developers on the branch want to do. "Branches' commit

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

See Changes: [aajisaka] MAPREDUCE-6580. Test failure: TestMRJobsWithProfiler. Contributed by [aajisaka] HADOOP-12952. BUILDING example of zero-docs dist should skip javadocs. --

[jira] [Created] (HADOOP-12957) Limit the number of outstanding async calls

Xiaobing Zhou created HADOOP-12957: -- Summary: Limit the number of outstanding async calls Key: HADOOP-12957 URL: https://issues.apache.org/jira/browse/HADOOP-12957 Project: Hadoop Common

Build failed in Jenkins: Hadoop-common-trunk-Java8 #1237

See Changes: [wang] HADOOP-12947. Update documentation Hadoop Groups Mapping to add static -- [...truncated 3872 lines...] [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile

Re: Branch policy question

Thanks for digging that up, Chris. That is completely what I would have expected but began questioning it given this thread. I think that Allen's use of a feature branch for this effort makes sense and that he should have the freedom to choose his commit policy for the branch. The tricky part

Re: Branch policy question

CTR is- and always has been- admissible in a branch. On Wed, Mar 23, 2016 at 2:11 PM, Steve Loughran wrote: > Given that only one +1 is needed to merge a non-branch patch, he could in > theory convert the entire branch into a single .patch for review. Not that > I'd

[jira] [Created] (HADOOP-12958) PhantomReference for filesystem statistics can trigger OOM

Jason Lowe created HADOOP-12958: --- Summary: PhantomReference for filesystem statistics can trigger OOM Key: HADOOP-12958 URL: https://issues.apache.org/jira/browse/HADOOP-12958 Project: Hadoop Common

Build failed in Jenkins: Hadoop-common-trunk-Java8 #1233

See Changes: [aajisaka] MAPREDUCE-6656. [NNBench] OP_DELETE operation isn't working after -- [...truncated 3846 lines...] [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile

Re: Branch policy question

> On Mar 22, 2016, at 6:46 PM, Gangumalla, Uma wrote: > >> is it possible for me to setup a branch, self review+commit to that >> branch, then request a branch merge? > Basically this is something like Commit-Then-Review(here review later) > process right. I have not

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

See Changes: [aajisaka] MAPREDUCE-6656. [NNBench] OP_DELETE operation isn't working after -- [...truncated 5243 lines...] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:

RE: [VOTE] Accept Chimera as new Apache Commons Component

Nice proposal. The high performance crypto offering is nice to be broadly accessible. Thanks. Non-binding +1. Regards, Kai -Original Message- From: Chris Nauroth [mailto:cnaur...@hortonworks.com] Sent: Wednesday, March 23, 2016 5:47 AM To: common-dev@hadoop.apache.org; Commons

Re: [VOTE] Accept Chimera as new Apache Commons Component

+1 Gary On Mon, Mar 21, 2016 at 1:45 AM, Benedikt Ritter wrote: > Hi all, > > after long discussions I think we have gathered enough information to > decide whether we want to accept the Chimera project as a new Apache > Commons component. > > Proposed name: Apache Commons

Build failed in Jenkins: Hadoop-common-trunk-Java8 #1238

See Changes: [junping_du] YARN-4820. ResourceManager web redirects in HA mode drops query -- [...truncated 3874 lines...] [INFO] Compiling 2 source files to

Re: Branch policy question

Thanks Chris N for digging back on this details. The main concern on this question was started like ³Since it¹s nearly impossible for me to get timely reviews for some build and script changes Š.². So, Even for CTR process, review is needed thing at some point. I have one question here is CTR

Build failed in Jenkins: Hadoop-common-trunk-Java8 #1232

See Changes: [aajisaka] MAPREDUCE-6580. Test failure: TestMRJobsWithProfiler. Contributed by [aajisaka] HADOOP-12952. BUILDING example of zero-docs dist should skip javadocs. --