You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by Vinod Kumar Vavilapalli <vi...@hortonworks.com> on 2015/06/01 19:45:32 UTC
Re: 2.7.1 status
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 <cn...@hortonworks.com> wrote:
> 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" <lm...@apache.org> wrote:
>
>> 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 <
>> vinodkv@hortonworks.com> wrote:
>>
>>> 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 <ec...@apache.org> wrote:
>>>
>>>> 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
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
Starting release process now.
Thanks
+Vinod
> On Jun 24, 2015, at 12:15 PM, Vinod Kumar Vavilapalli <vi...@hortonworks.com> 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 two. This time for real.
>
> Thanks
> +Vinod
>
>
>> On Jun 15, 2015, at 2:58 PM, Vinod Kumar Vavilapalli <vi...@hortonworks.com> wrote:
>>
>> 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 <vi...@hortonworks.com> wrote:
>>>
>>> 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 <cn...@hortonworks.com> wrote:
>>>
>>>> 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" <lm...@apache.org> wrote:
>>>>
>>>>> 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 <
>>>>> vinodkv@hortonworks.com> wrote:
>>>>>
>>>>>> 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 <ec...@apache.org> wrote:
>>>>>>
>>>>>>> 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
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
Starting release process now.
Thanks
+Vinod
> On Jun 24, 2015, at 12:15 PM, Vinod Kumar Vavilapalli <vi...@hortonworks.com> 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 two. This time for real.
>
> Thanks
> +Vinod
>
>
>> On Jun 15, 2015, at 2:58 PM, Vinod Kumar Vavilapalli <vi...@hortonworks.com> wrote:
>>
>> 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 <vi...@hortonworks.com> wrote:
>>>
>>> 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 <cn...@hortonworks.com> wrote:
>>>
>>>> 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" <lm...@apache.org> wrote:
>>>>
>>>>> 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 <
>>>>> vinodkv@hortonworks.com> wrote:
>>>>>
>>>>>> 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 <ec...@apache.org> wrote:
>>>>>>
>>>>>>> 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
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
Starting release process now.
Thanks
+Vinod
> On Jun 24, 2015, at 12:15 PM, Vinod Kumar Vavilapalli <vi...@hortonworks.com> 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 two. This time for real.
>
> Thanks
> +Vinod
>
>
>> On Jun 15, 2015, at 2:58 PM, Vinod Kumar Vavilapalli <vi...@hortonworks.com> wrote:
>>
>> 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 <vi...@hortonworks.com> wrote:
>>>
>>> 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 <cn...@hortonworks.com> wrote:
>>>
>>>> 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" <lm...@apache.org> wrote:
>>>>
>>>>> 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 <
>>>>> vinodkv@hortonworks.com> wrote:
>>>>>
>>>>>> 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 <ec...@apache.org> wrote:
>>>>>>
>>>>>>> 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
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
Starting release process now.
Thanks
+Vinod
> On Jun 24, 2015, at 12:15 PM, Vinod Kumar Vavilapalli <vi...@hortonworks.com> 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 two. This time for real.
>
> Thanks
> +Vinod
>
>
>> On Jun 15, 2015, at 2:58 PM, Vinod Kumar Vavilapalli <vi...@hortonworks.com> wrote:
>>
>> 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 <vi...@hortonworks.com> wrote:
>>>
>>> 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 <cn...@hortonworks.com> wrote:
>>>
>>>> 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" <lm...@apache.org> wrote:
>>>>
>>>>> 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 <
>>>>> vinodkv@hortonworks.com> wrote:
>>>>>
>>>>>> 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 <ec...@apache.org> wrote:
>>>>>>
>>>>>>> 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
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
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 <vi...@hortonworks.com> wrote:
>
> 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 <vi...@hortonworks.com> wrote:
>>
>> 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 <cn...@hortonworks.com> wrote:
>>
>>> 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" <lm...@apache.org> wrote:
>>>
>>>> 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 <
>>>> vinodkv@hortonworks.com> wrote:
>>>>
>>>>> 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 <ec...@apache.org> wrote:
>>>>>
>>>>>> 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
Posted by Tsuyoshi Ozawa <oz...@apache.org>.
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
<vi...@hortonworks.com> wrote:
> 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 <vi...@hortonworks.com> wrote:
>>
>> 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 <cn...@hortonworks.com> wrote:
>>
>>> 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" <lm...@apache.org> wrote:
>>>
>>>> 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 <
>>>> vinodkv@hortonworks.com> wrote:
>>>>
>>>>> 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 <ec...@apache.org> wrote:
>>>>>
>>>>>> 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
Posted by Tsuyoshi Ozawa <oz...@apache.org>.
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
<vi...@hortonworks.com> wrote:
> 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 <vi...@hortonworks.com> wrote:
>>
>> 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 <cn...@hortonworks.com> wrote:
>>
>>> 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" <lm...@apache.org> wrote:
>>>
>>>> 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 <
>>>> vinodkv@hortonworks.com> wrote:
>>>>
>>>>> 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 <ec...@apache.org> wrote:
>>>>>
>>>>>> 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
Posted by Tsuyoshi Ozawa <oz...@apache.org>.
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
<vi...@hortonworks.com> wrote:
> 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 <vi...@hortonworks.com> wrote:
>>
>> 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 <cn...@hortonworks.com> wrote:
>>
>>> 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" <lm...@apache.org> wrote:
>>>
>>>> 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 <
>>>> vinodkv@hortonworks.com> wrote:
>>>>
>>>>> 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 <ec...@apache.org> wrote:
>>>>>
>>>>>> 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
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
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 <vi...@hortonworks.com> wrote:
>
> 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 <vi...@hortonworks.com> wrote:
>>
>> 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 <cn...@hortonworks.com> wrote:
>>
>>> 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" <lm...@apache.org> wrote:
>>>
>>>> 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 <
>>>> vinodkv@hortonworks.com> wrote:
>>>>
>>>>> 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 <ec...@apache.org> wrote:
>>>>>
>>>>>> 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
Posted by Tsuyoshi Ozawa <oz...@apache.org>.
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
<vi...@hortonworks.com> wrote:
> 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 <vi...@hortonworks.com> wrote:
>>
>> 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 <cn...@hortonworks.com> wrote:
>>
>>> 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" <lm...@apache.org> wrote:
>>>
>>>> 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 <
>>>> vinodkv@hortonworks.com> wrote:
>>>>
>>>>> 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 <ec...@apache.org> wrote:
>>>>>
>>>>>> 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
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
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 <vi...@hortonworks.com> wrote:
>
> 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 <vi...@hortonworks.com> wrote:
>>
>> 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 <cn...@hortonworks.com> wrote:
>>
>>> 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" <lm...@apache.org> wrote:
>>>
>>>> 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 <
>>>> vinodkv@hortonworks.com> wrote:
>>>>
>>>>> 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 <ec...@apache.org> wrote:
>>>>>
>>>>>> 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
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
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 <vi...@hortonworks.com> wrote:
>
> 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 <vi...@hortonworks.com> wrote:
>>
>> 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 <cn...@hortonworks.com> wrote:
>>
>>> 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" <lm...@apache.org> wrote:
>>>
>>>> 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 <
>>>> vinodkv@hortonworks.com> wrote:
>>>>
>>>>> 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 <ec...@apache.org> wrote:
>>>>>
>>>>>> 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
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
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 <vi...@hortonworks.com> wrote:
>
> 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 <cn...@hortonworks.com> wrote:
>
>> 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" <lm...@apache.org> wrote:
>>
>>> 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 <
>>> vinodkv@hortonworks.com> wrote:
>>>
>>>> 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 <ec...@apache.org> wrote:
>>>>
>>>>> 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
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
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 <vi...@hortonworks.com> wrote:
>
> 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 <cn...@hortonworks.com> wrote:
>
>> 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" <lm...@apache.org> wrote:
>>
>>> 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 <
>>> vinodkv@hortonworks.com> wrote:
>>>
>>>> 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 <ec...@apache.org> wrote:
>>>>
>>>>> 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
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
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 <vi...@hortonworks.com> wrote:
>
> 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 <cn...@hortonworks.com> wrote:
>
>> 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" <lm...@apache.org> wrote:
>>
>>> 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 <
>>> vinodkv@hortonworks.com> wrote:
>>>
>>>> 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 <ec...@apache.org> wrote:
>>>>
>>>>> 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
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
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 <vi...@hortonworks.com> wrote:
>
> 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 <cn...@hortonworks.com> wrote:
>
>> 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" <lm...@apache.org> wrote:
>>
>>> 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 <
>>> vinodkv@hortonworks.com> wrote:
>>>
>>>> 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 <ec...@apache.org> wrote:
>>>>
>>>>> HADOOP-12001 should probably be added to the blocker list since it's a
>>>>> regression that can keep ldap from working.
>>>>
>>>>
>>
>>
>
>