hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arpit Agarwal <aagar...@hortonworks.com>
Subject Re: HDFS-6376
Date Wed, 28 May 2014 20:28:52 GMT
The wiki instructions are outdated. I will update them later this week
unless someone else does so first.

AFAIK the 2.4.1 release is imminent so this will likely go in 2.5.

On Wed, May 28, 2014 at 11:43 AM, <dlmarion@comcast.net> wrote:

> Thanks for the reply. I was following the instructions found at [1]. I'm
> not a committer. Is there a way to communicate to which version I would
> like the patch backported? Would I set the target version to 2.4.1 and the
> fix version to the version of trunk?
> [1] http://wiki.apache.org/hadoop/HowToContribute#Naming_your_patch
> ----- Original Message -----
> From: "Andrew Wang" <andrew.wang@cloudera.com>
> To: hdfs-dev@hadoop.apache.org
> Sent: Wednesday, May 28, 2014 2:34:29 PM
> Subject: Re: HDFS-6376
> Hey Dave,
> The build bot requires the patch to be made against trunk. We then backport
> it to branch-2 and branch-2.4 from trunk.
> Committers typically use their best judgement when doing the backport; if
> it's not straightforward, I'll do some additional checking, but if it's
> clean, I normally just build it, run the changed tests, and then commit.
> Best,
> Andrew
> On Wed, May 28, 2014 at 11:28 AM, <dlmarion@comcast.net> wrote:
> > I’m trying to complete this issue, but I am unable to get it to build in
> > Jenkins. The patch applies for my locally. Is there a known issue at this
> > time with the 2.4 branch build? Any help would be appreciated. Thanks.
> >
> > - Dave
> >

NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message