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 > <vino...@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 <cnaur...@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" <lmc...@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 < >>> vino...@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 <ecl...@apache.org> wrote: >>>> >>>>> HADOOP-12001 should probably be added to the blocker list since it's a >>>>> regression that can keep ldap from working. >>>> >>>> >> >> > >
