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 0D3C5D177 for ; Thu, 30 May 2013 18:53:41 +0000 (UTC) Received: (qmail 31141 invoked by uid 500); 30 May 2013 18:53:38 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 30972 invoked by uid 500); 30 May 2013 18:53:38 -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 30840 invoked by uid 99); 30 May 2013 18:53:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 May 2013 18:53:37 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [76.96.30.80] (HELO qmta08.emeryville.ca.mail.comcast.net) (76.96.30.80) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 May 2013 18:53:29 +0000 Received: from omta04.emeryville.ca.mail.comcast.net ([76.96.30.35]) by qmta08.emeryville.ca.mail.comcast.net with comcast id iGav1l0030lTkoCA8Jsndc; Thu, 30 May 2013 18:52:47 +0000 Received: from boudnik.org ([24.4.185.157]) by omta04.emeryville.ca.mail.comcast.net with comcast id iJsm1l00G3QAh8g8QJsmaQ; Thu, 30 May 2013 18:52:46 +0000 Received: from mail.boudnik.org (localhost [127.0.0.1]) by boudnik.org (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id r4UIqj9S011289; Thu, 30 May 2013 11:52:45 -0700 Received: (from cos@localhost) by mail.boudnik.org (8.14.3/8.14.3/Submit) id r4UIqjVN011288; Thu, 30 May 2013 11:52:45 -0700 X-Authentication-Warning: mail.boudnik.org: cos set sender to cos@apache.org using -f Date: Thu, 30 May 2013 11:52:45 -0700 From: Konstantin Boudnik To: common-dev@hadoop.apache.org Cc: hdfs-dev@hadoop.apache.org, mapreduce-dev@hadoop.apache.org, yarn-dev@hadoop.apache.org Subject: Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha Message-ID: <20130530185245.GM27292@linspire.com> References: <20130525034836.GB3423@tpx> <03EE2601-2DF2-409F-A171-A307DF86D750@hortonworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <03EE2601-2DF2-409F-A171-A307DF86D750@hortonworks.com> X-Organization: It's something of 'Cos User-Agent: Mutt/1.5.18 (2008-05-17) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369939967; bh=Pje8HB6QbJDNXZD5iGH3niUNx3tPY5TpfZxZwqImP2E=; h=Received:Received:Received:Received:Date:From:To:Subject: Message-ID:MIME-Version:Content-Type; b=EN4E6h3qxwopbKMZHjYBjfwVRf0Gf+RQd7mFMAgM97BwSY3ZvcD5rNMRcezg0Ryk2 9qbpvD5hAQEr9ic/+JNofKgXY08SMmOWEjmJZjl3yRaYVzVOJqmUCaMaknhTXHAgwb hV655GQqKHE8Ljx5u5PAL4prWzKQYykAH83HVrNb5XKAiIAQ0oMVI1fVG3Vzx8b2jZ 4oPXXRbUxWRmcFXm/t1GdTQfyt6R3sappP5vorV/58hSWiCm+7EAT1a0Bzm2NIG8ap UL5OZGxDPbkiwDSDViyirGvKLWiShm4HhUbBRIkjH7PolI4Sc7cCrPtx7a/RcL0mbr AR8Sd4XJKn4Zw== X-Virus-Checked: Checked by ClamAV on apache.org On Thu, May 30, 2013 at 10:57AM, Arun C Murthy wrote: > I see you just re-opened MAPREUDCE-5211. > > Why not include MAPREDUCE-5211 as well rather than create one release per patch? Arun, it is unclear if MAPREDUCE-5211 has implications in 2.0.4 as per https://issues.apache.org/jira/browse/MAPREDUCE-5211?focusedCommentId=13670574&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13670574 Hence, there's a good chance that it never will be backported. And I don't have any plans to created 'a release per patch'. > Also, this is the first time we are seeing a four-numbered scheme in Hadoop. > Why not call this 2.0.5-alpha? There were precedents in four-numbered schemes before: 0.20.20[3-5].0 comes to mind. As for 2.0.5-alpha: The release numbering games and votes that had happened in the last few weeks are very confusing. Some of them never been concluded, the branches are moved and artifact versions seem to be colliding. 2.0.4.x seems to work well for the stabilization purposes and it will allow to unblock downstream and integration projects quickly. Cos > Arun > > On May 24, 2013, at 8:48 PM, Konstantin Boudnik wrote: > > > All, > > > > I have created a release candidate (rc0) for hadoop-2.0.4.1-alpha that I would > > like to release. > > > > 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. > > > > 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-rc0 > > > > The maven artifacts are available via repository.apache.org. > > > > Please try the release bits and vote; the vote will run for the usual 7 days. > > > > Thanks for your voting > > Cos > > > >