Here we go again. The blocker / critical tickets ballooned up a lot, I see 64 now! : https://issues.apache.org/jira/issues/?filter=12334985
Also, the docs target (mvn package -Pdocs -DskipTests) is completely busted on branch-2, I figured I have to backport a whole bunch of patches that are only on trunk, and may be more fixes on top of that *sigh* I’ll start pushing for progress for an RC in a week or two. Any help towards this, reviewing/committing outstanding patches and contributing to open items is greatly appreciated. Thanks +Vinod > On Feb 9, 2016, at 11:51 AM, Vinod Kumar Vavilapalli <vino...@apache.org> > wrote: > > Sure. The last time I checked, there were 20 odd blocker/critical tickets too > that’ll need some of my time. > > Given that, if you can get them in before a week, we should be good. > > +Vinod > >> On Feb 5, 2016, at 1:19 PM, Subramaniam V K <subru...@gmail.com> wrote: >> >> Vinod, >> >> Thanks for initiating the 2.8 release thread. We are in late review stages >> for YARN-4420 (Add REST API for listing reservations) and YARN-2575 (Adding >> ACLs for reservation system), hoping to get them by next week. Any chance >> you can put off cutting 2.8 by a week as we are planning to deploy >> ReservationSystem and these are critical for that? >> >> Cheers, >> Subru >> >> On Thu, Feb 4, 2016 at 3:17 PM, Chris Nauroth <cnaur...@hortonworks.com> >> wrote: >> >>> FYI, I've just needed to raise HDFS-9761 to blocker status for the 2.8.0 >>> release. >>> >>> --Chris Nauroth >>> >>> >>> >>> >>> On 2/3/16, 6:19 PM, "Karthik Kambatla" <ka...@cloudera.com> wrote: >>> >>>> Thanks Vinod. Not labeling 2.8.0 stable sounds perfectly reasonable to me. >>>> Let us not call it alpha or beta though, it is quite confusing. :) >>>> >>>> On Wed, Feb 3, 2016 at 8:17 PM, Gangumalla, Uma <uma.ganguma...@intel.com >>>> >>>> wrote: >>>> >>>>> Thanks Vinod. +1 for 2.8 release start. >>>>> >>>>> Regards, >>>>> Uma >>>>> >>>>> On 2/3/16, 3:53 PM, "Vinod Kumar Vavilapalli" <vino...@apache.org> >>>>> wrote: >>>>> >>>>>> Seems like all the features listed in the Roadmap wiki are in. I¹m >>>>> going >>>>>> to try cutting an RC this weekend for a first/non-stable release off of >>>>>> branch-2.8. >>>>>> >>>>>> Let me know if anyone has any objections/concerns. >>>>>> >>>>>> Thanks >>>>>> +Vinod >>>>>> >>>>>>> On Nov 25, 2015, at 5:59 PM, Vinod Kumar Vavilapalli >>>>>>> <vino...@apache.org> wrote: >>>>>>> >>>>>>> Branch-2.8 is created. >>>>>>> >>>>>>> As mentioned before, the goal on branch-2.8 is to put improvements / >>>>>>> fixes to existing features with a goal of converging on an alpha >>>>> release >>>>>>> soon. >>>>>>> >>>>>>> Thanks >>>>>>> +Vinod >>>>>>> >>>>>>> >>>>>>>> On Nov 25, 2015, at 5:30 PM, Vinod Kumar Vavilapalli >>>>>>>> <vino...@apache.org> wrote: >>>>>>>> >>>>>>>> Forking threads now in order to track all things related to the >>>>>>>> release. >>>>>>>> >>>>>>>> Creating the branch now. >>>>>>>> >>>>>>>> Thanks >>>>>>>> +Vinod >>>>>>>> >>>>>>>> >>>>>>>>> On Nov 25, 2015, at 11:37 AM, Vinod Kumar Vavilapalli >>>>>>>>> <vino...@apache.org> wrote: >>>>>>>>> >>>>>>>>> I think we¹ve converged at a high level w.r.t 2.8. And as I just >>>>> sent >>>>>>>>> out an email, I updated the Roadmap wiki reflecting the same: >>>>>>>>> https://wiki.apache.org/hadoop/Roadmap >>>>>>>>> <https://wiki.apache.org/hadoop/Roadmap> >>>>>>>>> >>>>>>>>> I plan to create a 2.8 branch EOD today. >>>>>>>>> >>>>>>>>> The goal for all of us should be to restrict improvements & fixes >>>>> to >>>>>>>>> only (a) the feature-set documented under 2.8 in the RoadMap wiki >>>>> and >>>>>>>>> (b) other minor features that are already in 2.8. >>>>>>>>> >>>>>>>>> Thanks >>>>>>>>> +Vinod >>>>>>>>> >>>>>>>>> >>>>>>>>>> On Nov 11, 2015, at 12:13 PM, Vinod Kumar Vavilapalli >>>>>>>>>> <vino...@hortonworks.com <mailto:vino...@hortonworks.com>> wrote: >>>>>>>>>> >>>>>>>>>> - Cut a branch about two weeks from now >>>>>>>>>> - Do an RC mid next month (leaving ~4weeks since branch-cut) >>>>>>>>>> - As with 2.7.x series, the first release will still be called as >>>>>>>>>> early / alpha release in the interest of >>>>>>>>>> ‹ gaining downstream adoption >>>>>>>>>> ‹ wider testing, >>>>>>>>>> ‹ yet reserving our right to fix any inadvertent >>>>> incompatibilities >>>>>>>>>> introduced. >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>> >>> >
