Return-Path: X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 052F2F4CC for ; Fri, 31 May 2013 06:42:14 +0000 (UTC) Received: (qmail 29045 invoked by uid 500); 31 May 2013 06:42:09 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 28756 invoked by uid 500); 31 May 2013 06:42:09 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 28696 invoked by uid 99); 31 May 2013 06:42:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 May 2013 06:42:08 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of vinodkv@hortonworks.com designates 209.85.161.182 as permitted sender) Received: from [209.85.161.182] (HELO mail-gg0-f182.google.com) (209.85.161.182) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 May 2013 06:42:01 +0000 Received: by mail-gg0-f182.google.com with SMTP id q2so284245ggc.41 for ; Thu, 30 May 2013 23:41:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=HaTaXh2PB2oEo4RpVomwj+RmwynPeqeeQivN2US0cyM=; b=FaJ2fcvaQpHeaCNalSE/6OW6GENphgXA1msrthV7kUo2O9Rgg1l0ni/ir0yJviDXZV 2k9zJuCoYISAnI2daDZrToThRSkGe5riG/JW+FA58c1fnxi5eMK4NbW59hWmKYwdSsHx VucsMg0xGBQN5n60emrFuO2WikZkJ4qUmN+7RgLe4HLvji2tlnBbPnMTiuxulDrnCoIR iVTZSbrLsT4+oQbVncJpN5L9ZCNH3VzY5OyYe0/GlGEYb+oSTKIMVOcVgrrefbmFSAy7 10u/2nbW8f3fM2VsjFcXxHPIVS1LuXg/6QR6Bm4zvly+fj4KE9R05Z3DNxqDlAfqxoJO O+xg== X-Received: by 10.236.22.230 with SMTP id t66mr5881787yht.70.1369982500082; Thu, 30 May 2013 23:41:40 -0700 (PDT) Received: from ?IPv6:2602:306:ce97:c9d0:d574:8269:d145:2acf? ([2602:306:ce97:c9d0:d574:8269:d145:2acf]) by mx.google.com with ESMTPSA id d24sm34437287yhi.17.2013.05.30.23.41.35 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 May 2013 23:41:37 -0700 (PDT) Subject: Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: multipart/alternative; boundary="Apple-Mail=_0F65D3DB-FC4A-4594-A654-47A2F3BFB7C8" From: Vinod Kumar Vavilapalli In-Reply-To: <20130531055034.GB3600@tpx> Date: Thu, 30 May 2013 23:41:34 -0700 Cc: hdfs-dev@hadoop.apache.org, "yarn-dev@hadoop.apache.org" , "mapreduce-dev@hadoop.apache.org" Message-Id: <16777B86-7E49-44B3-B6B6-1BB22ED64901@apache.org> References: <20130525034836.GB3423@tpx> <03EE2601-2DF2-409F-A171-A307DF86D750@hortonworks.com> <20130530213904.GN27292@linspire.com> <20130530222505.GP27292@linspire.com> <20130531005102.GU27292@linspire.com>

<20130531055034.GB3600@tpx> To: common-dev@hadoop.apache.org X-Mailer: Apple Mail (2.1283) X-Gm-Message-State: ALoCoQl5p47yjgLNyEcVxpo4711RuvTXpReqRIwroIqsk1OSQpB/jlTDe4A/L12YsZPdxpMogHYk X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_0F65D3DB-FC4A-4594-A654-47A2F3BFB7C8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii This started out as something and ended up as something else altogether. In any case, I think you should give a fresh heads up outside this = thread. There are a bunch of commits and merges happening into branch-2 and thus = 2.0.5, so it'll be safe to have an explicit hold-off/all-clear = signaling. Otherwise you'll be racing with others on CHANGES.txt commits = and the JIRA version set. Thanks, +Vinod On May 30, 2013, at 10:50 PM, Konstantin Boudnik wrote: > Thanks Alejandro, >=20 > that's what my plan for the morning. Thanks for putting together the > check-list - would be easier for me not to miss anything. I am aiming = to have > the bits out by noon or so. Appreciate the help! >=20 > Cos >=20 > On Thu, May 30, 2013 at 08:41PM, Alejandro Abdelnur wrote: >> Konstantin, Cos, >>=20 >> As we change from 2.0.4.1 to 2.0.5 you'll need to do the following >> housekeeping as you work the new RC. >>=20 >> * rename the svn branch >> * update the versions in the POMs >> * update the CHANGES.txt in trunk, branch-2 and the release branch >> * change the current 2.0.5 version in JIRA to 2.1.0, create a new = 2.0.5 >> version, change the fix version of the 2 JIRAs that make the RC >>=20 >> Thanks. >>=20 >>=20 >> On Thu, May 30, 2013 at 6:18 PM, Chris Douglas = wrote: >>=20 >>> On Thu, May 30, 2013 at 5:51 PM, Konstantin Boudnik >>> wrote: >>>> I have no issues of changing the version to 2.0.5-alpha and = restarting >>> to vote >>>> for the release content, e.g. 2 bug fixes. Shall I call 3 days = re-vote >>> because >>>> of the number change? >>>=20 >>> +1 Sounds great. >>>=20 >>>> Does the result of bylaw vote nullifies the unfinished vote started = by >>> Arun? >>>> Sorry, I am dense, apparently. >>>=20 >>> Yes, nobody should feel bound by either vote. The bylaw change >>> clarifies that release plans are for RMs to solicit feedback and = gauge >>> PMC support for an artifact, not pre-approvals for doing work. >>>=20 >>>> Can we limit the vote thread to the merits of the release then? >>>=20 >>> Happily. >>>=20 >>>> That sound like adding an insult to injury, if my forth-language = skills >>> do not >>>> mislead me. >>>=20 >>> They do mislead you, or I've expressed the point imprecisely. We can >>> take this offline. -C >>>=20 >>>>>>>> On Thu, May 30, 2013 at 01:48PM, Chris Douglas wrote: >>>>>>>>> On Thu, May 30, 2013 at 10:57 AM, Arun C Murthy < >>> acm@hortonworks.com> wrote: >>>>>>>>>> Why not include MAPREDUCE-4211 as well rather than create one >>> release per patch? >>>>>>>>>=20 >>>>>>>>> =46rom Cos's description, it sounded like these were backports = of >>> fixes >>>>>>>>> to help Sqoop2 and fix some build issues. If it's not just to >>> fixup >>>>>>>>> leftover bugs in 2.0.4 *once* so downstream projects can = integrate >>>>>>>>> against 2.0.4.1, and this a release series, then I've = completely >>>>>>>>> misunderstood the purpose. >>>>>>>>>=20 >>>>>>>>> Cos, are you planning 2.0.4.2? >>>>>>>>>=20 >>>>>>>>>> Also, this is the first time we are seeing a four-numbered >>> scheme in Hadoop. Why not call this 2.0.5-alpha? >>>>>>>>>=20 >>>>>>>>> Good point. Since it contains only backports from branch-2, it >>> would >>>>>>>>> make sense for it to be an intermediate release. >>>>>>>>>=20 >>>>>>>>> I shouldn't have to say this, but I'm changing my vote to -1 >>> while we >>>>>>>>> work this out. -C >>>>>>>>>=20 >>>>>>>>>> On May 24, 2013, at 8:48 PM, Konstantin Boudnik wrote: >>>>>>>>>>=20 >>>>>>>>>>> All, >>>>>>>>>>>=20 >>>>>>>>>>> I have created a release candidate (rc0) for >>> hadoop-2.0.4.1-alpha that I would >>>>>>>>>>> like to release. >>>>>>>>>>>=20 >>>>>>>>>>> This is a stabilization release that includes fixed for a >>> couple a of issues >>>>>>>>>>> discovered in the testing with BigTop 0.6.0 release = candidate. >>>>>>>>>>>=20 >>>>>>>>>>> The RC is available at: >>> http://people.apache.org/~cos/hadoop-2.0.4.1-alpha-rc0/ >>>>>>>>>>> The RC tag in svn is here: >>> = http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.4.1-alpha-r= c0 >>>>>>>>>>>=20 >>>>>>>>>>> The maven artifacts are available via repository.apache.org. >>>>>>>>>>>=20 >>>>>>>>>>> Please try the release bits and vote; the vote will run for >>> the usual 7 days. >>>>>>>>>>>=20 >>>>>>>>>>> Thanks for your voting >>>>>>>>>>> Cos >>>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>=20 >>>=20 >>=20 >>=20 >>=20 >> --=20 >> Alejandro --Apple-Mail=_0F65D3DB-FC4A-4594-A654-47A2F3BFB7C8--