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 seen we followed this approa

[jira] [Created] (HADOOP-12956) Inevitable Log4j2 migration via slf4j

Gopal V created HADOOP-12956: Summary: Inevitable Log4j2 migration via slf4j Key: HADOOP-12956 URL: https://issues.apache.org/jira/browse/HADOOP-12956 Project: Hadoop Common Issue Type: Improveme

Re: Branch policy question

Just to clarify, we are talking about a feature branch in which Allen and others that are working on the branch could commit without requiring 3 +1’s. Then, at some point, we will need 3 +1’s to merge the branch to trunk. Correct? I think that if we have a set of usecases that are being added and

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

See Changes: [cmccabe] HDFS-10189. PacketResponder#toString should include the downstreams for -- [...truncated 3846 lines...] [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile

Re: Branch policy question

> 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 seen we followed this approach here( not sure if I missed some branches followed that). Even t

[jira] [Created] (HADOOP-12955) checknative failed when checking ISA-L library

Kai Zheng created HADOOP-12955: -- Summary: checknative failed when checking ISA-L library Key: HADOOP-12955 URL: https://issues.apache.org/jira/browse/HADOOP-12955 Project: Hadoop Common Issue Ty

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

See

Re: Branch policy question

If the underlying problem is lack of reviewers for these improvements, how about a design doc giving some motivation for the improvements and explaining how they'll be implemented? Then we can decide if a branch or a few JIRAs on trunk makes more sense. The description for HADOOP-12857 is just "l

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

See Changes: [gtcarrera9] MAPREDUCE-6110. JobHistoryServer CLI throws NullPointerException with -- [...truncated 3847 lines...] [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile

[jira] [Created] (HADOOP-12954) Add a way to change hadoop.security.token.service.use_ip

Robert Kanter created HADOOP-12954: -- Summary: Add a way to change hadoop.security.token.service.use_ip Key: HADOOP-12954 URL: https://issues.apache.org/jira/browse/HADOOP-12954 Project: Hadoop Common

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

+1 (non-binding) --Chris Nauroth On 3/21/16, 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 Crypto >

[jira] [Created] (HADOOP-12953) New API for libhdfs to get FileSystem object as a proxy user

Uday Kale created HADOOP-12953: -- Summary: New API for libhdfs to get FileSystem object as a proxy user Key: HADOOP-12953 URL: https://issues.apache.org/jira/browse/HADOOP-12953 Project: Hadoop Common

Re: Branch policy question

VOTE threads tend to get more eyes than random JIRAs. On Tue, Mar 22, 2016 at 1:23 PM, 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. > > On Tue, Mar 22, 2016 at 10:56 AM, Allen Witten

Re: Branch policy question

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. On Tue, Mar 22, 2016 at 10:56 AM, Allen Wittenauer < allenwittena...@yahoo.com.invalid> wrote: > > > On Mar 22, 2016, at 10:49 AM, larry mccay wrote: > > > > Th

Re: Branch policy question

> On Mar 22, 2016, at 10:49 AM, larry mccay wrote: > > That sounds like a reasonable approach and valid use of branches to me. > > Perhaps a set of functional tests could be provided/identified that would > help the review process by showing backward compatibility along with new > extensions fo

Re: Branch policy question

That sounds like a reasonable approach and valid use of branches to me. Perhaps a set of functional tests could be provided/identified that would help the review process by showing backward compatibility along with new extensions for things like dynamic commands? On Tue, Mar 22, 2016 at 12:14 PM

Branch policy question

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 basically looking at doing this for HADOOP-12857 + HADOOP-12930 and their subtasks e

[jira] [Created] (HADOOP-12952) /BUILDING example of zero-docs dist should skip javadocs

Steve Loughran created HADOOP-12952: --- Summary: /BUILDING example of zero-docs dist should skip javadocs Key: HADOOP-12952 URL: https://issues.apache.org/jira/browse/HADOOP-12952 Project: Hadoop Commo