I recommend giving the JACC report another look. I set up a parameterized jenkins job which you can trigger manually for branch-2.8:
https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/ On Wed, Nov 30, 2016 at 4:06 PM, Junping Du <j...@hortonworks.com> wrote: > Hi Sangjin and all, > > That sounds good. If anyone have priority fix to backport , please > nominate it by following this email thread or ping me on JIRA directly. And > I agree that we should keep in mind that our bar for 2.8 release should be > high now as we want to move quickly on this release. Non-critical fixes can > wait for next one. > > Any other comments and suggestions? > > > Thanks, > > > Junping > > > ________________________________ > From: sjl...@gmail.com <sjl...@gmail.com> on behalf of Sangjin Lee < > sj...@apache.org> > Sent: Wednesday, November 30, 2016 3:24 PM > To: Junping Du > Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; > mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; Vinod > Vavilapalli; Jian He; Wangda Tan; sj...@twitter.com > Subject: Re: [Continued] [Release thread] 2.8.0 release activities > > Thanks for picking this up Junping! > > I heard on email threads and offline discussions that there may be > interests in porting some fixes from branch-2 to branch-2.8. I still feel > that the bar should be pretty high to do that, but it might be good to have > folks suggest some critical fixes that need to be released sooner. Thoughts? > > On Tue, Nov 29, 2016 at 8:50 PM, Junping Du <j...@hortonworks.com<mailto:jd > u...@hortonworks.com>> wrote: > Hi folks, > Per asked by Vinod offline, I would like to continue the effort to > push 2.8 release out in next several weeks. The plan is as following: > - We only have 5 blockers and 3 critical issues ( > https://s.apache.org/6kwx) so far, and most of them are in good progress > now. I put them all on apache ciwiki ( https://cwiki.apache.org/ > confluence/display/HADOOP/Hadoop+2.8+Release) and will do daily monitor > and update on these issues in next couple of weeks. > - When all blocker/critical issues are gone (target EOD is Dec. 10), > I will push out all major/minor issues that is open. So if you are working > on some major issues and target for release in 2.8, please keep track of > our release status and your work progress. > - I will create RC immediately once our 2.8 target issues are clean > (especially for blocker and critical issues) for voting process. > > I hope we can make it within year 2016, best before Xmas holiday. And > I need help from all of you. :) > > > Thanks, > > Junping > > ________________________________________ > From: Vinod Kumar Vavilapalli <vino...@apache.org<mailto:vin > o...@apache.org>> > Sent: Monday, July 25, 2016 2:57 PM > To: Jian He > Cc: mapreduce-...@hadoop.apache.org<mailto:mapreduce-...@hadoop.apache.org>; > yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>; > hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>; > common-...@hadoop.apache.org<mailto:common-...@hadoop.apache.org> > Subject: Re: [Release thread] 2.8.0 release activities > > Thanks for all that great help moving this release forward, Jian, Sangjin, > Wangda et al! Appreciate it. > > The License / Notice fix is finally in. And I pushed out a 2.7.3 RC0 last > week. > > I only see 9 blocker / critical fixes pending for 2.8.0 - > https://issues.apache.org/jira/issues/?filter=12334985. Let’s do this! > > Thanks > +Vinod > > > On May 11, 2016, at 6:04 PM, Jian He <j...@hortonworks.com<mailto:jh > e...@hortonworks.com>> wrote: > > > > For MapReduce/YARN, I closed a few staled ones. Only 4 jiras needs > attention for 2.8 > > > > MAPREDUCE-6288 > > YARN-1815 > > YARN-4685 > > YARN-4844 > > > > The rest are either improvements or long-standing issues and does not > qualify release blocker, IMO. > > I think we’ll try to get these 4 jiras in asap. The rest will be on best > effort, resolve as much as possible and move them out if not resolved in > time. > > > > Jian > > > > On May 11, 2016, at 5:37 PM, Wangda Tan <wheele...@gmail.com<mailto:wh > eele...@gmail.com><mailto:wheele...@gmail.com<mailto:wheele...@gmail.com>>> > wrote: > > > > Sounds good to me :). > > > > Jian and I have looked at all existing 2.8.0 blockers and criticals > today. > > To me more than half of MR/YARN blockers/criticals of 2.8 should be moved > > out. Left comments on these JIRAs asked original owners, plan to update > > target version of these JIRAs early next week. > > > > Will keep this thread updated. > > > > Thanks, > > Wangda > > > > > > On Wed, May 11, 2016 at 5:06 PM, Sangjin Lee <sj...@apache.org<mailto: > sj...@apache.org><mailto:sj...@apache.org<mailto:sj...@apache.org>>> > wrote: > > > > How about this? I'll review the HADOOP/HDFS bugs in that list to come up > > with true blockers for 2.8.0 or JIRAs that are close to being ready. I'll > > report the list here. Then folks can chime in if you agree > > > > Perhaps Wangda, you can go over the YARN/MR bugs. Sound like a plan? > > > > Thanks, > > Sangjin > > > > On Wed, May 11, 2016 at 4:26 PM, Wangda Tan <wheele...@gmail.com<mailto: > wheele...@gmail.com><mailto:wheele...@gmail.com<mailto:wheele...@gmail.com>>> > wrote: > > > > +1, we should close such staled JIRAs to avoid doing unnecessary checks > > for > > every releases. > > > > I'm working on reviewing YARN/MR critical/blocker patches currently, it > > gonna very helpful if someone else can help with reviewing Common/HDFS > > JIRAs. > > > > Thanks, > > Wangda > > > > > > On Wed, May 11, 2016 at 4:20 PM, Sangjin Lee <sj...@apache.org<mailto: > sj...@apache.org><mailto:sj...@apache.org<mailto:sj...@apache.org>>> > wrote: > > > > Where do we stand in terms of closing out blocker/critical issues for > > 2.8.0? I still see 50 open JIRAs in Vinod's list: > > https://issues.apache.org/jira/issues/?filter=12334985 > > > > But I see a lot of JIRAs with no patches or very stale patches. It > > would be > > a good exercise to come up with the list of JIRAs that we need to block > > 2.8.0 for and focus our attention on closing them out. Thoughts? > > > > Thanks, > > Sangjin > > > > On Sat, Apr 23, 2016 at 5:05 AM, Steve Loughran <ste...@hortonworks.com< > mailto:ste...@hortonworks.com><mailto:ste...@hortonworks.com<mailto: > ste...@hortonworks.com>> > > > > wrote: > > > > > > On 23 Apr 2016, at 01:24, Vinod Kumar Vavilapalli < > > vino...@apache.org<mailto:vino...@apache.org><mailto:vino...@apache.org > <mailto:vino...@apache.org>>> > > wrote: > > > > We are not converging - there’s still 58 more. I need help from the > > community in addressing / review 2.8.0 blockers. If folks can start > > with > > reviewing Patch available tickets, that’ll be great. > > > > > > > > > > I'm still doing the s3a stuff, other people testing and reviewing this > > stuff welcome. > > > > in particular, I could do with others playing with this patch of mine, > > which adds counters and things into S3a, based on the azure > > instrumentation > > > > https://issues.apache.org/jira/browse/HADOOP-13028 > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org<mailto: > yarn-dev-unsubscr...@hadoop.apache.org> > For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org<mailto: > yarn-dev-h...@hadoop.apache.org> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org > <mailto:mapreduce-dev-unsubscr...@hadoop.apache.org> > For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org > <mailto:mapreduce-dev-h...@hadoop.apache.org> > > >
