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 EF65B95CC for ; Wed, 6 Jun 2012 21:10:57 +0000 (UTC) Received: (qmail 35567 invoked by uid 500); 6 Jun 2012 21:10:54 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 35392 invoked by uid 500); 6 Jun 2012 21:10:54 -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 35375 invoked by uid 99); 6 Jun 2012 21:10:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jun 2012 21:10:54 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of eli@cloudera.com designates 209.85.217.176 as permitted sender) Received: from [209.85.217.176] (HELO mail-lb0-f176.google.com) (209.85.217.176) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jun 2012 21:10:47 +0000 Received: by lboj14 with SMTP id j14so55827lbo.35 for ; Wed, 06 Jun 2012 14:10:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=B3H3sisbEWIzwy3PeDoh/jwFjd7cdkpUzuFm314zZ5g=; b=RV6zztatYQI7M96EtMKur45BKT9x8Y/5aI08i2TVbNOwxF9UG3zQfK9fhupIVqwEqN 1G6ESH1chYrxKDqhef9JGdXKoCd3tGUEdSfuwA4Lg8/1RJehk9+/vg99W2MaZpUSQkQ1 EU6wYYTkv4QpKOY00EwiL0Z+NRbTHt6imbEGN2b1JYsoHwp84HwBx+flW/t5ZykqluHi jgK+1W1Ka/y4y++JFqmL2Pz8CGMjjY0EMZaOFNEhhXBlav1BK2H6OjFML4kDm2g39k9v 7ak6W3h561d6mBwflOsZaHX6I2dULv7/bg2f+Uzf+f/g2ke56q+qhAhK66YnEMTcbgea 7Y4g== MIME-Version: 1.0 Received: by 10.112.48.169 with SMTP id m9mr85150lbn.93.1339017026987; Wed, 06 Jun 2012 14:10:26 -0700 (PDT) Received: by 10.112.5.100 with HTTP; Wed, 6 Jun 2012 14:10:26 -0700 (PDT) In-Reply-To: References: Date: Wed, 6 Jun 2012 14:10:26 -0700 Message-ID: Subject: Re: Clarification about 2.* branches From: Eli Collins To: general@hadoop.apache.org Cc: common-dev@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQkQFEWDoyu5DxfOKYoyNFPfv11wK4+JAYaKSLLI7l2FnxAtlnU//z/VL6CVu6aGHKw8rimb Hey Vinod, Out of curiosity, why delete the branch? Might make spelunking for svn revs that correspond to a release hard. If we're deleting old release branches might as well delete the others (branch-0.23.0, branch-0.23.0-rc0, branch-0.23.1, branch-0.23.2, etc) as well? Thanks, Eli On Wed, Jun 6, 2012 at 1:52 PM, Vinod Kumar Vavilapalli wrote: > > > I checked with Nicholas also who did the only merge into branch-2.0.0-alp= ha after the release and got a confirmation that I can delete the branch. > > Removing the branch now. > > Thanks, > +Vinod > > > On Jun 5, 2012, at 5:45 PM, Arun C Murthy wrote: > >> +1 for blowing away branch-2.0.0-alpha now, we have the release tag if n= ecessary. >> >> thanks, >> Arun >> >> On Jun 5, 2012, at 4:40 PM, Vinod Kumar Vavilapalli wrote: >> >>> Hi, >>> >>> I see two branches for 2.* now: branch-2 and branch-2.0.0-alpha and two= sections in CHANGES.txt: 2.0.1-alpha unreleased and 2.0.0-alpha released. = It is a little confusing, seems like branch-2.0.0-alpha was a staging branc= h for the release and can be thrown away. >>> >>> Anyone committing patches to both branch-2 and branch-2.0.0-alpha? If n= ot, I'll blow away the later and rename the section in CHANGES.txt to branc= h-2. >>> >>> Thanks, >>> +Vinod >> >> -- >> Arun C. Murthy >> Hortonworks Inc. >> http://hortonworks.com/ >> >> >