Per our discussion on JIRA and here, I was okay with this backport.

I want to get back to the RC quickly now, so went ahead and pulled the patch 
into 2.7.2 myself.

Thanks
+Vinod

> On Dec 10, 2015, at 4:06 PM, Konstantin Boudnik <c...@apache.org> wrote:
> 
> Vinod, are you Ok with me putting it into 2.7.2?
> 
> Cos
> 
> On Mon, Nov 30, 2015 at 01:25PM, Vinod Kumar Vavilapalli wrote:
>> I think we should get it in, I am still stuck on a couple of HDFS patches.
>> 
>> But I was not sure overall if the patch was right. Commented on the JIRA 
>> regarding the same.
>> 
>> Thanks
>> +Vinod
>> 
>>> On Nov 27, 2015, at 1:54 AM, Steve Loughran <ste...@hortonworks.com> wrote:
>>> 
>>> well, I'm not going to block it...it doesn't add anything more to the pom 
>>> dependencies that aren't there right now
>>> 
>>>> On 26 Nov 2015, at 18:51, Konstantin Boudnik <c...@apache.org> wrote:
>>>> 
>>>> On Wed, Nov 25, 2015 at 01:51PM, Steve Loughran wrote:
>>>>> 
>>>>>> On 25 Nov 2015, at 02:48, Konstantin Boudnik <c...@apache.org> wrote:
>>>>>> 
>>>>>> Vinod, hopefully it isn't too late for a quick fix to be included into 
>>>>>> 2.7.2
>>>>>> (sorry for jumping too late on this train). The JIRA in question is
>>>>>> HADOOP-12415 and I have committed it to trunk and branch-2 already.
>>>>>> 
>>>>>> Please let me know if this is still Ok to add into 2.7.2 as it seems to 
>>>>>> be
>>>>>> going through a respin. Thanks in advance,
>>>>>> 
>>>>>> Cos
>>>>>> 
>>>>> 
>>>>> 
>>>>> can you hold it off until 2.7.3? 2.7.2 was tested and we shoudn't be 
>>>>> making
>>>>> more changes now, even if its just to the POMs
>>>> 
>>>> It's up to you guys, the fix is small but pretty critical IMO. The change 
>>>> in
>>>> question is literally breaking the build from the get go. In Bigtop we had 
>>>> to
>>>> patch 2.7.1 so we at least can build it into the stack. 
>>>> 
>>>> For the users using official release tarball it won't simply work unless 
>>>> they
>>>> are going to patch it themselves.
>>>> 
>>>> Cos
>>> 
>>> 
>> 

Reply via email to