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 C3254D1E3 for ; Mon, 10 Sep 2012 20:50:17 +0000 (UTC) Received: (qmail 38490 invoked by uid 500); 10 Sep 2012 20:50:15 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 38398 invoked by uid 500); 10 Sep 2012 20:50:15 -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 38390 invoked by uid 99); 10 Sep 2012 20:50:15 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Sep 2012 20:50:15 +0000 Received: from localhost (HELO mail-lb0-f176.google.com) (127.0.0.1) (smtp-auth username omalley, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Sep 2012 20:50:15 +0000 Received: by lboi15 with SMTP id i15so1824703lbo.35 for ; Mon, 10 Sep 2012 13:50:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.152.144.2 with SMTP id si2mr2230028lab.26.1347310213277; Mon, 10 Sep 2012 13:50:13 -0700 (PDT) Received: by 10.112.22.73 with HTTP; Mon, 10 Sep 2012 13:50:13 -0700 (PDT) In-Reply-To: References: Date: Mon, 10 Sep 2012 13:50:13 -0700 Message-ID: Subject: Re: [VOTE] 0.23.3 release From: "Owen O'Malley" To: common-dev@hadoop.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Sep 10, 2012 at 12:19 PM, Robert Evans wrote: > Thanks for the info Owen I was not aware of that, I can see at the > beginning of the twiki > http://wiki.apache.org/hadoop/HowToReleasePostMavenization that it is kin= d > of implied by the skip this section comment. But, I was just confused > because to do an official release I need to change the version number in > several different places, and I didn=C2=B9t think that is was all that ko= sher > to do that directly in the tags area. Please don't make edits in the tags area. > It also seems to be a bit different > then what is happening on branch-2. Branch 2 also has issues, which we've also been ironing out. The branch-2.0.1-alpha and branch-2.0.2-alpha will be deleted soon. > I was planning on deleting the branch once the vote for 0.23.3 finished, That would be fine. > but I can delete it now if you would prefer and the roll back the version > numbers on branch-0.23 to be 0.23.3? Or would it be 0.23.3-SNAPSHOT still= ? You can wait for 0.23.3 to clean up. The only odd part of that is that the 0.23.3 tag won't be on the branch-0.23. With Ant, we could just override the version on the command line. Clearly Maven is a little pickier. You could: 1. Set the version to 0.23.3 2. Check in 3. Make the tag 4. Set the version to 0.23.4-SNAPSHOT 5. Check in I'd also be ok with just waiting with 4+5 until the vote passes. Thoughts? (Of course as discussed this would be more about 0.23.4 :) ) > I also want to be sure that we want to not allow anyone to check anythin= g > in for a week+ on branch-0.23. There are a few things I know of that are > almost ready but are not Blockers. Sure. That makes sense. -- Owen