Kumar
Vavilapalli
Subject: Re: A 2.7.1 release to follow up 2.7.0
+1 for roll out 2.7.0 soon and continuing stabilization in 2.7.1.
Agree with Karthik, it's better to exclude all improvements unless it turns out
to blocking something.
In terms of jdiff, we have done the compatibility check for quite
t: Re: A 2.7.1 release to follow up 2.7.0
There's a couple of S3a fixes coming along which could go into a 2.7.1; they've
been held back to avoid rushing them in to 2.7.0 last-minute.
> On 9 Apr 2015, at 20:33, Junping Du wrote:
>
> +1 (non-binding).
> The plan sounds rea
ystem
>> in many aspects.
>>
>> Thanks,
>>
>> Junping
>>
>> From: Arpit Agarwal
>> Sent: Thursday, April 09, 2015 8:23 PM
>> To: hdfs-...@hadoop.apache.org; common-dev@hadoop.apache.org;
>> yarn-...@hadoop.apache.org; mapreduce-...@hado
op.apache.org; common-dev@hadoop.apache.org;
> yarn-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org
> Cc: Vinod Kumar Vavilapalli
> Subject: Re: A 2.7.1 release to follow up 2.7.0
>
> +1 for 2.7.1 and +1 for promoting it to 'stable', assuming it includes no new
> feat
To: hdfs-...@hadoop.apache.org; common-dev@hadoop.apache.org;
yarn-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org
Cc: Vinod Kumar Vavilapalli
Subject: Re: A 2.7.1 release to follow up 2.7.0
+1 for 2.7.1 and +1 for promoting it to 'stable', assuming it includes no new
f
+1 for 2.7.1 and +1 for promoting it to 'stable', assuming it includes no new
features or gratuitous improvements.
Arpit
On 4/9/15, 11:48 AM, "Vinod Kumar Vavilapalli" wrote:
>Hi all,
>
>I feel like we haven't done a great job of maintaining the previous 2.x
>releases. Seeing as how long 2
+1, full agreement with both Vinod and Karthik. Thanks!
Chris Nauroth
Hortonworks
http://hortonworks.com/
On 4/9/15, 12:07 PM, "Karthik Kambatla" wrote:
>Inline.
>
>On Thu, Apr 9, 2015 at 11:48 AM, Vinod Kumar Vavilapalli
>> wrote:
>
>> Hi all,
>>
>> I feel like we haven't done a great jo
Inline.
On Thu, Apr 9, 2015 at 11:48 AM, Vinod Kumar Vavilapalli wrote:
> Hi all,
>
> I feel like we haven't done a great job of maintaining the previous 2.x
> releases. Seeing as how long 2.7.0 release has taken, I am sure we will
> spend more time stabilizing it, fixing issues etc.
>
> I propo
Hi all,
I feel like we haven't done a great job of maintaining the previous 2.x
releases. Seeing as how long 2.7.0 release has taken, I am sure we will
spend more time stabilizing it, fixing issues etc.
I propose that we immediately follow up 2.7.0 with a 2.7.1 within 2-3
weeks. The focus obvious
