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 A42EFF645 for ; Sat, 1 Jun 2013 00:40:22 +0000 (UTC) Received: (qmail 33774 invoked by uid 500); 1 Jun 2013 00:40:21 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 33484 invoked by uid 500); 1 Jun 2013 00:40: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 33470 invoked by uid 99); 1 Jun 2013 00:40:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Jun 2013 00:40:21 +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 (athena.apache.org: domain of azuryyyu@gmail.com designates 209.85.223.172 as permitted sender) Received: from [209.85.223.172] (HELO mail-ie0-f172.google.com) (209.85.223.172) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Jun 2013 00:40:16 +0000 Received: by mail-ie0-f172.google.com with SMTP id 17so5743576iea.31 for ; Fri, 31 May 2013 17:39:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WGNoKuNSzOCwleGHHE0AjQsF4ljoYhvZ+BjOYzAdf/Y=; b=vEM0FIhYSUc7yq8ggQfiiREuYdiO1gV7P8c3uJc8pktVlMDh6slaQEyTS+BqOEgWzK 2DjTphloadhiTeCa+74TJdUf4MaJPmZIpJOSX/4HarwymeTPzGs7TFnlJb5R+n+B6i9R H2KtWKSwPhMVWz5IA348Wpc7gMDBRsWDNTkZj0RlrAR/GTf65zupjLUNvSUO1HsARYDM rq0ODtnF6L0a1aX+gdWY/sxw1gB+fw045RZi8mYOPduwdlOpceySTkk0Btc8kPHFxjMO Dg+s13mkHCe/wg9TNvVxNvSrHud3lBZbe5yCtcUwocEG9LQnylKSf47X6tTJOvodtGN2 H/uQ== MIME-Version: 1.0 X-Received: by 10.50.130.11 with SMTP id oa11mr2781654igb.108.1370047195973; Fri, 31 May 2013 17:39:55 -0700 (PDT) Received: by 10.64.61.67 with HTTP; Fri, 31 May 2013 17:39:55 -0700 (PDT) Received: by 10.64.61.67 with HTTP; Fri, 31 May 2013 17:39:55 -0700 (PDT) In-Reply-To: References: <20130525034836.GB3423@tpx> <03EE2601-2DF2-409F-A171-A307DF86D750@hortonworks.com> <20130530213904.GN27292@linspire.com> <20130530222505.GP27292@linspire.com> <20130531005102.GU27292@linspire.com>

<20130531194544.GE17179@linspire.com> Date: Sat, 1 Jun 2013 08:39:55 +0800 Message-ID: Subject: Re: Heads up: moving from 2.0.4.1-alpha to 2.0.5-alpha From: Azuryy Yu To: hdfs-dev@hadoop.apache.org Cc: common-dev@hadoop.apache.org Content-Type: multipart/alternative; boundary=047d7b418b3b710dd704de0cf87c X-Virus-Checked: Checked by ClamAV on apache.org --047d7b418b3b710dd704de0cf87c Content-Type: text/plain; charset=ISO-8859-1 2.1.0-alpha is 2.0.5-beta actually. --Send from my Sony mobile. On Jun 1, 2013 8:14 AM, "Ted Yu" wrote: > I am currently testing HBase 0.95 using 2.0.5-SNAPSHOT artifacts. > > Would 2.1.0-SNAPSHOT maven artifacts be available after tomorrow's change ? > > Thanks > > On Fri, May 31, 2013 at 12:45 PM, Konstantin Boudnik > wrote: > > > Guys, > > > > I will be performing some changes wrt to moving 2.0.4.1 release candidate > > to > > 2.0.5 space. As outline below by Alejandro: > > > > 1. I will create new 2.0.5-alpha branch from the current head of > > 2.0.4-alpha > > that contains 2.0.4.1 changes > > 2. consequently, set the artifacts version on the new branch to be > > 2.0.5-alpha > > 3. the CHANGES.txt will be updated accordingly on the new 2.0.5 branch > > 4. At this point I can cut an RC and put it out for re-vote. The staging > > can > > be done after the next two steps. > > > > I will be doing all these modifications in the next hour or so. > > > > Tomorrow at 1 pm PDT I would like to: > > 1. update the version of the artifacts on branch-2 to become > 2.1.0-SNAPSHOT > > 2. update the CHANGES.txt in the trunk and branch-2 to reflect new > version > > names > > 3. at this point it should safe to do the staging for 2.0.5-alpha RC > > > > To avoid any collisions during the last two steps - especially 2. - I > would > > ask everyone to hold off the modifications of the CHANGES.txt files on > > trunk > > and branch-2 between 1 pm and 2 pm PDT. > > > > Please let me know if you see any flaw above, questions. > > Cos > > > > > 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. > > > > > > * 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 > > > > > I renamed 2.0.5-beta to 2.1.0-beta and 2.0.4.1-alpha to 2.0.5-alpha > > versions > > > in jira for HADOOP, HDFS, YARN & MAPREDUCE. > > > > > Please take care of the rest. > > > > > Also, in branch-2, the version should be 2.1.0-SNAPSHOT. > > > --047d7b418b3b710dd704de0cf87c--