Re: 2.7.1 status

2015-06-28 Thread Vinod Kumar Vavilapalli
Starting release process now. Thanks +Vinod > On Jun 24, 2015, at 12:15 PM, Vinod Kumar Vavilapalli > wrote: > > With a bit of effort from a bunch of contributors/committers, we are finally > down to zero blocker/critical issues. > > Unless, the situation changes, I’ll roll an RC in a day or

Re: 2.7.1 status

2015-06-24 Thread Vinod Kumar Vavilapalli
With a bit of effort from a bunch of contributors/committers, we are finally down to zero blocker/critical issues. Unless, the situation changes, I’ll roll an RC in a day or two. This time for real. Thanks +Vinod > On Jun 15, 2015, at 2:58 PM, Vinod Kumar Vavilapalli > wrote: > > We are do

Re: 2.7.1 status

2015-06-15 Thread Tsuyoshi Ozawa
Hi Vinod, Thank you for working to release 2.7! YARN-3798 looks a critical issue for branch-2.7. I'll mark it as a blocker of 2.7.1 if possible. Thanks, - Tsuyoshi On Tue, Jun 16, 2015 at 6:58 AM, Vinod Kumar Vavilapalli wrote: > We are down to one blocker and a few critical tickets. I’ll try t

Re: 2.7.1 status

2015-06-15 Thread Vinod Kumar Vavilapalli
We are down to one blocker and a few critical tickets. I’ll try to push out an RC in a day or two. Thanks +Vinod > On Jun 1, 2015, at 10:45 AM, Vinod Kumar Vavilapalli > wrote: > > Tx for the move on that JIRA, folks. > > https://issues.apache.org/jira/issues/?filter=12331550 still shows 4

Re: 2.7.1 status

2015-06-01 Thread Vinod Kumar Vavilapalli
Nijel >> >> -Original Message- >> From: Vinod Kumar Vavilapalli [mailto:vino...@hortonworks.com] >> Sent: 23 May 2015 01:02 >> To: Hadoop Common; hdfs-dev@hadoop.apache.org; yarn-...@hadoop.apache.org; >> mapreduce-...@hadoop.apache.org >> Cc: Vin

Re: 2.7.1 status

2015-06-01 Thread Vinod Kumar Vavilapalli
Tx for the move on that JIRA, folks. https://issues.apache.org/jira/issues/?filter=12331550 still shows 4 blockers / 4 criticals. I'm going to start pushing them in/out. Thanks +Vinod On May 27, 2015, at 3:20 PM, Chris Nauroth wrote: > Thanks, Larry. I have marked HADOOP-11934 as a blocker

Re: 2.7.1 status

2015-05-27 Thread Chris Nauroth
Thanks, Larry. I have marked HADOOP-11934 as a blocker for 2.7.1. I have reviewed and +1'd it. I can commit it after we get feedback from Jenkins. --Chris Nauroth On 5/26/15, 12:41 PM, "larry mccay" wrote: >Hi Vinod - > >I think that https://issues.apache.org/jira/browse/HADOOP-11934 shou

Re: 2.7.1 status

2015-05-26 Thread larry mccay
Hi Vinod - I think that https://issues.apache.org/jira/browse/HADOOP-11934 should also be added to the blocker list. This is a critical bug in our ability to protect the LDAP connection password in LdapGroupsMapper. thanks! --larry On Tue, May 26, 2015 at 3:32 PM, Vinod Kumar Vavilapalli < vino

Re: 2.7.1 status

2015-05-26 Thread Vinod Kumar Vavilapalli
Tx for reporting this, Elliot. Made it a blocker, not with a deeper understanding of the problem. Can you please chime in with your opinion and perhaps code reviews? Thanks +Vinod On May 26, 2015, at 10:48 AM, Elliott Clark wrote: > HADOOP-12001 should probably be added to the blocker list si

Re: 2.7.1 status

2015-05-26 Thread Elliott Clark
HADOOP-12001 should probably be added to the blocker list since it's a regression that can keep ldap from working.

Re: 2.7.1 status

2015-05-22 Thread Vinod Kumar Vavilapalli
Been a while since 2.7.0 release. I am going to do a scan of outstanding issues this weekend and start the push. There are 7 blockers/criticals as of now: https://issues.apache.org/jira/issues/?filter=12331550 I couldn't send notes to downstream projects as I originally anticipated. But from o

2.7.1 status

2015-04-23 Thread Vinod Kumar Vavilapalli
As we talked before [1], I am going to start the push for 2.7.1 [2]. Here are the things I am going to do, with help from others in the community - Review current 2.7.1 content to make sure only bug fixes went in - Review 2.8 to see if any important bug fixes didn't get merged into 2.7.1 - Send