Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C46F1200BE2 for ; Thu, 1 Dec 2016 01:18:46 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id C3074160B19; Thu, 1 Dec 2016 00:18:46 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8FFFB160B13 for ; Thu, 1 Dec 2016 01:18:45 +0100 (CET) Received: (qmail 81472 invoked by uid 500); 1 Dec 2016 00:18:44 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 81460 invoked by uid 99); 1 Dec 2016 00:18:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Dec 2016 00:18:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id B0711C1B98 for ; Thu, 1 Dec 2016 00:18:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.48 X-Spam-Level: ** X-Spam-Status: No, score=2.48 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=cloudera-com.20150623.gappssmtp.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Ri5AzQcu3qOf for ; Thu, 1 Dec 2016 00:18:41 +0000 (UTC) Received: from mail-ua0-f181.google.com (mail-ua0-f181.google.com [209.85.217.181]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 6DF265F5F8 for ; Thu, 1 Dec 2016 00:18:41 +0000 (UTC) Received: by mail-ua0-f181.google.com with SMTP id 51so231394094uai.1 for ; Wed, 30 Nov 2016 16:18:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudera-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=rZFGCSardGMsCCy9SRIaYORLJ85nie0jSgrYM7ANcXs=; b=jUiJxpWkpV6ZhnIFzjgPLFAh0tHemPgxqEpRuiT38xktFFCqQGd2yVuhVfhLl/GIZj atiTfio58EfdjF5KvSwA+kmEbsCfYmVVafE5574c6mgs2+pia9ilu80LIgLQTDUf+r0B CRDy3R4RJ0Xu/qcanUWNJmyIZyS/krud1N9yYNwICwNztO818mfrfYMkUSIpdYvNWEqG m6JMsXbHCodocDFH1H73c4D9v1Xu+UFWXflf6CgnVAU5kVuadL632nI/MF0STckgUvKR XmhgKNOtcxj0OlkmxAadZLQIEjrqvl0Lcbd+uaOEGyTzQXbJsxXmoKQ2xuWr3rn6eYDT GX7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=rZFGCSardGMsCCy9SRIaYORLJ85nie0jSgrYM7ANcXs=; b=XW/79UAFfVQ8ssaodaVgaR4Yscn0ZxCRkhg2k4vl4NUlEEU2GUT5lfrXMhLc+DnGL1 d3Mu3wHr3wx5ECVx0jNpSeS7//ZUVzGWRCMLtPaALmZekh0x70XWrpHc1Wh5uUJJ5qe2 HlMp9l6w0ddCHWXQyLIiYM1g+cyn7HKpnvY9qfCijfRKBvDTa8Pg70+s1H575pkB2KC7 hENhFZXifbgIP+glf7NyEl27R80xv8gFJCp2eeBO4NGHklOYo0MD4mDmtkH/xnrMRl+m +6ChE5b6ACw8yK7yjc42zWe5kxwHXCpgZabACi18GxHHwHr+OtozSZLW/tNcKsIjdkZg 3YgQ== X-Gm-Message-State: AKaTC01MiSXOOgB/JrTccJGOE0D3nMdIUAHyysYWYY+DE3Jc1CTLYjvo8BCQpC4qKmAFue6GWDnKFMLgyrhU7WBg X-Received: by 10.159.49.11 with SMTP id m11mr28230757uab.178.1480551520953; Wed, 30 Nov 2016 16:18:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.31.21.137 with HTTP; Wed, 30 Nov 2016 16:18:20 -0800 (PST) In-Reply-To: <1480550805462.62858@hortonworks.com> References: <0C22896E-D77B-4DE4-99A2-9D81E150779C@hortonworks.com> <49120AE6-98D9-4CC2-A6A6-4C322A25F1D6@apache.org> <2A5F3F89-C79B-42BD-98AC-246CF33D4C47@apache.org> <33E01D1B-C416-464F-8E18-0B368A52DFF3@apache.org> <4B44247B-AFB2-4803-BDB0-251A8270F98C@apache.org> <2F9B8811-8240-454A-8599-64BE4B15CE2F@apache.org> <7CCEC640-5BCA-4ECC-976B-8630F4C0DD72@apache.org> <33841919-A63C-40BC-992D-9B98424BFBFC@hortonworks.com> <09457A47-B7F1-49C0-96CF-AA2AB07C6E2A@hortonworks.com> <5AD22D82-0F7C-4443-8FBB-B1295CB5707D@apache.org> <1480481443907.45579@hortonworks.com> <1480550805462.62858@hortonworks.com> From: Andrew Wang Date: Wed, 30 Nov 2016 16:18:20 -0800 Message-ID: Subject: Re: [Continued] [Release thread] 2.8.0 release activities To: Junping Du Cc: Sangjin Lee , "common-dev@hadoop.apache.org" , "hdfs-dev@hadoop.apache.org" , "mapreduce-dev@hadoop.apache.org" , "yarn-dev@hadoop.apache.org" , Vinod Vavilapalli , Jian He , Wangda Tan , "sjlee@twitter.com" Content-Type: multipart/alternative; boundary=f403045e257e7a795005428dc393 archived-at: Thu, 01 Dec 2016 00:18:46 -0000 --f403045e257e7a795005428dc393 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 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. A= nd > I agree that we should keep in mind that our bar for 2.8 release should b= e > high now as we want to move quickly on this release. Non-critical fixes c= an > wait for next one. > > Any other comments and suggestions? > > > Thanks, > > > Junping > > > ________________________________ > From: sjlee0@gmail.com on behalf of Sangjin Lee < > sjlee@apache.org> > Sent: Wednesday, November 30, 2016 3:24 PM > To: Junping Du > Cc: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; > mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; Vinod > Vavilapalli; Jian He; Wangda Tan; sjlee@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 ha= ve > folks suggest some critical fixes that need to be released sooner. Though= ts? > > On Tue, Nov 29, 2016 at 8:50 PM, Junping Du 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 workin= g > 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. An= d > I need help from all of you. :) > > > Thanks, > > Junping > > ________________________________________ > From: Vinod Kumar Vavilapalli odkv@apache.org>> > Sent: Monday, July 25, 2016 2:57 PM > To: Jian He > Cc: mapreduce-dev@hadoop.apache.org; > yarn-dev@hadoop.apache.org; > hdfs-dev@hadoop.apache.org; > common-dev@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=3D12334985. Let=E2=80=99s d= o this! > > Thanks > +Vinod > > > On May 11, 2016, at 6:04 PM, Jian He 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=E2=80=99ll try to get these 4 jiras in asap. The rest will b= e 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 eeleast@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 mov= ed > > 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 sjlee@apache.org>>> > wrote: > > > > How about this? I'll review the HADOOP/HDFS bugs in that list to come u= p > > 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 wheeleast@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 sjlee@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=3D12334985 > > > > 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 mailto:stevel@hortonworks.com> stevel@hortonworks.com>> > > > > wrote: > > > > > > On 23 Apr 2016, at 01:24, Vinod Kumar Vavilapalli < > > vinodkv@apache.org >> > > wrote: > > > > We are not converging - there=E2=80=99s 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=E2=80=99ll 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-unsubscribe@hadoop.apache.org yarn-dev-unsubscribe@hadoop.apache.org> > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org yarn-dev-help@hadoop.apache.org> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org > > For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org > > > > --f403045e257e7a795005428dc393--