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 45424200BE2 for ; Thu, 1 Dec 2016 00:25:07 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 43BA8160B19; Wed, 30 Nov 2016 23:25:07 +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 690BB160B13 for ; Thu, 1 Dec 2016 00:25:06 +0100 (CET) Received: (qmail 31713 invoked by uid 500); 30 Nov 2016 23:25:05 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 31671 invoked by uid 99); 30 Nov 2016 23:25:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Nov 2016 23:25:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 74B31C1372; Wed, 30 Nov 2016 23:25:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.231 X-Spam-Level: ** X-Spam-Status: No, score=2.231 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id WvkB6P7wf4hd; Wed, 30 Nov 2016 23:25:00 +0000 (UTC) Received: from mail-yw0-f195.google.com (mail-yw0-f195.google.com [209.85.161.195]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id F2BA25F297; Wed, 30 Nov 2016 23:24:59 +0000 (UTC) Received: by mail-yw0-f195.google.com with SMTP id b66so16109483ywh.2; Wed, 30 Nov 2016 15:24:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=xHl//YO73H65Zv8lgmMa0waDAaWtadMIpUCpqVU+eYQ=; b=zDCsr0xd5sCMQ9AaMLOkvUMaNyo9LoAbeegQS4N9qdKKeHfVu/5wf6/Jv78obGb2d8 cK3H3a4pXoJwvSk5CcCsJMPwZewl0jEDlaqOVNekco0Qlt9mBvyiF3w+zpbUBNFbt8KB OQ3UJm4OHGtkhBdm6BZGgWvl2NSPf3CoOWbKf6Ax22XFCqwIzyK847vdPXuFCdy7bRz0 GDstP1PP06V/k31lKZPcW+yxwnDKRqqKgLGMlj2mR+q4vuhiYIM50hazpwWzvOOgdQ7t t8jVcyaZrOxpOLvaWeW/+J/A/YR1+9lm+oM9zMCCuAnHx2tBDKspcrI24n4D3F/n3cwt JLDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=xHl//YO73H65Zv8lgmMa0waDAaWtadMIpUCpqVU+eYQ=; b=MQ5GrfOet68Iz3n61sLRIPgg4OGbn3RAjYF2cEzUw9Q2FqtzZ86Bbz9ELCIv1v4CDh ZJBbMjuCl0mygd7LKLJynhuxrTSEHhEHwF1K4Oy6JAynhnqug6Xf/u7ztUkSSY+sHDq3 MLH84t8ccKxdfA9dXtcaM66Razb/Ih+Wlopl+GqnD8xZy1J2yzN1bjZJA8hAMGTneynn 6Rr2iRKGHziJSjL6hWFaTq55QFZajvlkeQpZbNavX/4oqAnmFS4GbwYKYSQbG5Cwvg7K 8kR6k9xGcBOiJE7VGVZ89VsQE0QGU85IzC3JAbujknxloshm0pHbP+0I0tqjXp/oTtU7 wn5w== X-Gm-Message-State: AKaTC032g7JRMYaf3NyZpWQWT/BD2ZwdLgvkvjZz0zIRNy/fupkuex7WbHIeUsBCYF5wq6uLrY0alrHu+KS1Cg== X-Received: by 10.157.1.36 with SMTP id 33mr22216873otu.65.1480548298539; Wed, 30 Nov 2016 15:24:58 -0800 (PST) MIME-Version: 1.0 Sender: sjlee0@gmail.com Received: by 10.183.11.75 with HTTP; Wed, 30 Nov 2016 15:24:37 -0800 (PST) In-Reply-To: <1480481443907.45579@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> From: Sangjin Lee Date: Wed, 30 Nov 2016 15:24:37 -0800 X-Google-Sender-Auth: P6khl9Ipaz7AaPU2lNZh1qBDFuo Message-ID: Subject: Re: [Continued] [Release thread] 2.8.0 release activities 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" Content-Type: multipart/alternative; boundary=94eb2c03c83e684af205428d03df archived-at: Wed, 30 Nov 2016 23:25:07 -0000 --94eb2c03c83e684af205428d03df Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 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 > 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 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> > > > > 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 > For additional commands, e-mail: 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 > > --94eb2c03c83e684af205428d03df--