Curious on the status of 2.7.3.... It seems that we still have two outstanding critical/blocker JIRAs:
1. [image: Bug] HADOOP-12893 Verify LICENSE.txt and NOTICE.txt <https://issues.apache.org/jira/browse/HADOOP-12893> 2. [image: Sub-task] HADOOP-13154 <https://issues.apache.org/jira/browse/HADOOP-13154>S3AFileSystem printAmazonServiceException/printAmazonClientException appear copy & paste of AWS examples <https://issues.apache.org/jira/browse/HADOOP-13154> But 45-ish when we include Majors as well. I know there are a number of critical issues with fixes that need to go out. What is the plan? On Tue, Apr 12, 2016 at 2:09 PM, Vinod Kumar Vavilapalli <vino...@apache.org > wrote: > Others and I committed a few, I pushed out a few. > > Down to just three now! > > +Vinod > > > On Apr 6, 2016, at 3:00 PM, Vinod Kumar Vavilapalli <vino...@apache.org> > wrote: > > > > Down to only 10 blocker / critical tickets ( > https://issues.apache.org/jira/issues/?filter=12335343 < > https://issues.apache.org/jira/issues/?filter=12335343>) now! > > > > Thanks > > +Vinod > > > >> On Mar 30, 2016, at 4:18 PM, Vinod Kumar Vavilapalli < > vino...@apache.org <mailto:vino...@apache.org>> wrote: > >> > >> Hi all, > >> > >> Got nudged about 2.7.3. Was previously waiting for 2.6.4 to go out > (which did go out mid February). Got a little busy since. > >> > >> Following up the 2.7.2 maintenance release, we should work towards a > 2.7.3. The focus obviously is to have blocker issues [1], bug-fixes and > *no* features / improvements. > >> > >> I hope to cut an RC in a week - giving enough time for outstanding > blocker / critical issues. Will start moving out any tickets that are not > blockers and/or won’t fit the timeline - there are 3 blockers and 15 > critical tickets outstanding as of now. > >> > >> Thanks, > >> +Vinod > >> > >> [1] 2.7.3 release blockers: > https://issues.apache.org/jira/issues/?filter=12335343 < > https://issues.apache.org/jira/issues/?filter=12335343> > > > >
