Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BF85A18495 for ; Thu, 7 Jan 2016 15:01:22 +0000 (UTC) Received: (qmail 5492 invoked by uid 500); 7 Jan 2016 15:01:22 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 5399 invoked by uid 500); 7 Jan 2016 15:01:21 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 5382 invoked by uid 99); 7 Jan 2016 15:01:21 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jan 2016 15:01:21 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 382201A027F for ; Thu, 7 Jan 2016 15:01:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.847 X-Spam-Level: ** X-Spam-Status: No, score=2.847 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_REPLYTO_END_DIGIT=0.25, HTML_MESSAGE=3, RP_MATCHES_RCVD=-0.554, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id kqZnSyfeEvG0 for ; Thu, 7 Jan 2016 15:01:09 +0000 (UTC) Received: from nm22-vm9.bullet.mail.gq1.yahoo.com (nm22-vm9.bullet.mail.gq1.yahoo.com [98.136.217.72]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 59C1320C6A for ; Thu, 7 Jan 2016 15:01:08 +0000 (UTC) Received: from [98.137.12.62] by nm22.bullet.mail.gq1.yahoo.com with NNFMP; 07 Jan 2016 15:01:00 -0000 Received: from [98.137.12.235] by tm7.bullet.mail.gq1.yahoo.com with NNFMP; 07 Jan 2016 15:01:00 -0000 Received: from [127.0.0.1] by omp1043.mail.gq1.yahoo.com with NNFMP; 07 Jan 2016 15:01:00 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 170212.93161.bm@omp1043.mail.gq1.yahoo.com X-YMail-OSG: BEi8RnEVM1mbIjcBBVkMDH4Tl2.KPpPq2mzCD_66Rfq5.7WV.6VPdbgjuVIQIB7 2HP3fe3qfYo0IoJeMLGqRgzaNbt1OWWVBPGpiR9klcC7gQVicd.F28QpaicfxC8KFj_e4.wOfB2Z 5AiGO6W6ief32fU3RtSZPsHHZ5KNAvRkwfOFewi2fS3G5MpttBJjwGJ.SWp1ylkNtfzH1SagnLSn C.FK08UW9OKMS.WbDqqEDaqhvbOcqZrN7tF8zPc9nAI3AmK3zJnDAFH9735XDzWellXY8HtdUTb3 _k01oTT9i1vQhZivPtMpCev8cPr4zTdU4RllfbjIoMOp0elnBWQkb4V0atmA4rSNBxouWgamW4B5 nIpnFrdAk7_AFHEKRFajKL_DiNIKve1Ju9icRiaXgq17Ldnikz3ydo0hgi02D9Frmt1GkboxGT7O sEPSRnMnS9uVQ_Uw7PomzxzW9BvS1hd4wdNsthA6lbBAceYtwu_ZM70tZ1MvV1LJ4TWzxsK3DwPP 2vRypZGsY1DcS1Hxcn7Dbj8YzNlFm Received: by 216.39.60.207; Thu, 07 Jan 2016 15:00:59 +0000 Date: Thu, 7 Jan 2016 15:00:59 +0000 (UTC) From: Eric Payne Reply-To: Eric Payne To: "mapreduce-dev@hadoop.apache.org" , "common-dev@hadoop.apache.org" , "yarn-dev@hadoop.apache.org" , "hdfs-dev@hadoop.apache.org" Cc: "junping_du@apache.org" , Sangjin Lee , Vinod Kumar Vavilapalli Message-ID: <295604101.1472895.1452178859197.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: <1452125269773.58595@hortonworks.com> References: <1452125269773.58595@hortonworks.com> Subject: Re: [DISCUSSION] Release Plan for Apache Hadoop 2.6.4 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1472894_1141725577.1452178859190" ------=_Part_1472894_1141725577.1452178859190 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thanks a lot, Junping Du, for managing these releases. Just one minor point:>=C2=A0=C2=A0 =C2=A0 -- Before 2.6.4 branch is cut off= , new commits coming as fix to 2.6.4 is good to commit/merge to trunk, bran= ch-2 and branch-2.6. I just want to remind everyone to not forget to also merge changes into bra= nch-2.7 and branch-2.8 as well, when changes are applicable, so we can main= tain consistency across those releases as well. Thanks,-Eric Payne =20 From: Junping Du To: "common-dev@hadoop.apache.org" ; "yarn-d= ev@hadoop.apache.org" ; "hdfs-dev@hadoop.apache= .org" ; "mapreduce-dev@hadoop.apache.org" =20 Cc: "junping_du@apache.org" ; Sangjin Lee ; Vinod Kumar Vavilapalli Sent: Wednesday, January 6, 2016 5:59 PM Subject: [DISCUSSION] Release Plan for Apache Hadoop 2.6.4 =20 Hello folks, =C2=A0 =C2=A0 =C2=A0 Hope everyone had a wonderful holiday and good rest in= passed weeks. We just had a 2.6.3 release on Dec.17 and now it is a good t= ime to look forward to the next branch-2.6 maintenance release - 2.6.4 in t= he beginning of new year. As usual, this release will be based on latest re= lease 2.6.3 but include a couple of critical/blocker bug fixes that identif= ied in community recently. Things Done/TODO: =C2=A0 + Schedule =C2=A0 =C2=A0 -- According to previous email discussion thread in community= , we are prefering fast-moving way (roughly as monthly) of releasing fixes = on branch-2.6. So I would expect this release could happen around end of Ja= n. or early of Feb. dependens on if RC & VOTE process going on smoothly. Al= so, it should be after release 2.7.2 to get rid of any possible disturb to = that release. =C2=A0 + Branch =C2=A0 =C2=A0 -- 2.6.4 will be based on branch-2.6, which has been open to = 2.6.4 commits for a while. I plan to branch out branch-2.6.4 sometime next = week according to status of target/fixed fixes. =C2=A0 =C2=A0 -- Before 2.6.4 branch is cut off, new commits coming as fix = to 2.6.4 is good to commit/merge to trunk, branch-2 and branch-2.6. =C2=A0 + Patches =C2=A0 =C2=A0 -- In last couple of days, I went through all critial/blocker= bug fixes in the coming 2.7.2 release and ping authors/committers on JIRA = to ask for the same effort on branch-2.6.4. I could do more rounds of the s= ame practice in case I could miss something helpful. Also, a kindly reminde= r from original author and committer is also appreciated. =C2=A0 =C2=A0 -- So far, 2.6.4 already has 18 fixes as list of [1] shows. H= owever, there are totally 55 fixes target for 2.6.4 for now [2], so there i= s still a large gap and we need to work harder to resolve these tickets as = many as we can and push out some non-critical ones to meet our promise of d= ate. =C2=A0 + Release =C2=A0 =C2=A0 -- Still too early to do anything directly related to RC. Wil= l work on resolve fixes in list of [2] first, and appreciate any help on th= is effort. Any thoughts? Especially on schedule and list of patches that should be inc= luded? Cheers, Junping [1] Tickets fixed in 2.6.4: http://s.apache.org/vJB [2] Tickets targets for 2.6.4: http://s.apache.org/JpE ________________________________________ From: Junping Du Sent: Thursday, December 17, 2015 1:36 PM To: common-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org Cc: hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; junping_du= @apache.org Subject: [RESULT] [VOTE] Release Apache Hadoop 2.6.3 RC0 Hi all in community, =C2=A0 =C2=A0 I give my binding +1 to close the vote for 2.6.3 RC0. With 18= +1s (10 binding), one +0 (non-binding) and no -1s, the vote passes. Thanks for everyone who tried the release candidate and voted. Thanks Vinod= , Sangjin and Steve to provide me advices on release process. I'll push the release bits and send out an announcement for 2.6.3 soon. Cheers, Junping ________________________________________ From: Xuan Gong Sent: Thursday, December 17, 2015 12:29 AM To: common-dev@hadoop.apache.org Cc: hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; yarn-dev@h= adoop.apache.org; junping_du@apache.org Subject: Re: [VOTE] Release Apache Hadoop 2.6.3 RC0 +1 (binding), Build and deploy the cluster from source code. Ran a few example jobs and passed successfully. Xuan Gong > On Dec 16, 2015, at 4:07 PM, Arpit Agarwal wro= te: > > +1 (binding) > > - Verified signatures for source and binary distributions > - Built jars from source with java 1.7.0_79 > - Deployed single-node pseudo-cluster > - Ran example map reduce jobs > - Ran hdfs admin commands, verified NN web UI shows expected usages > > > > On 12/11/15, 4:16 PM, "Junping Du" wrote: > >> >> Hi all developers in hadoop community, >>=C2=A0 I've created a release candidate RC0 for Apache Hadoop 2.6.3 (the = next maintenance release to follow up 2.6.2.) according to email thread of = release plan 2.6.3 [1]. Sorry for this RC coming a bit late as several bloc= ker issues were getting committed until yesterday. Below is the details: >> >> The RC is available for validation at: >> *http://people.apache.org/~junping_du/hadoop-2.6.3-RC0/ >> * >> >> The RC tag in git is: release-2.6.3-RC0 >> >> The maven artifacts are staged via repository.apache.org at: >> *https://repository.apache.org/content/repositories/orgapachehadoop-1025= /? >> * >> >> You can find my public key at: >> http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS >> >> Please try the release and vote. The vote will run for the usual 5 days. >> >> Thanks and happy weekend! >> >> >> Cheers, >> >> Junping >> >> >> [1]: 2.6.3 release plan: http://markmail.org/thread/nc2jogbgni37vu6y >> ------=_Part_1472894_1141725577.1452178859190--