Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Received-SPF: pass (athena.apache.org: domain of josh.elser@gmail.com
 designates 209.85.128.41 as permitted sender)
Message-ID: <52CE281A.3040402@gmail.com>
Date: Wed, 08 Jan 2014 23:39:54 -0500
From: Josh Elser <josh.elser@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: dev@accumulo.apache.org
Subject: Re: [DISCUSS] How to generate RC's
References: 
 <CAFAMeYJi4jNzUCnZ_mfygm-UuTf8b71LZqqLchvHypVDJx4KKQ@mail.gmail.com>
In-Reply-To: 
 <CAFAMeYJi4jNzUCnZ_mfygm-UuTf8b71LZqqLchvHypVDJx4KKQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Looks good to me. I don't think it's too much work in the big picture -- 
it's what's necessary to get it done properly given the tool.

The only ambiguity I see is in 3a), "make corrections _on x.y.z-SNAPSHOT_".

Let's make sure this (assuming there aren't any objections) gets up on 
the site.

- Josh

On 1/8/14, 7:58 PM, Mike Drob wrote:
> Taking this conversation from IRC because it probably needs to be on the
> mailing list at some point. Also, we'll want to update the site when we
> have something we are happy with. Thanks to Christopher and Josh for the
> thoughts they've already contributed to the discussion.
>
> We need a standard procedure for generating RCs that is:
> 1) Easily reproducible
> 2) Compatible with ongoing development
> 3) Compatible with our git branching model.
>
> The proposed process is:
> 1) Create an RC branch named x.y.z-rcN from (the tip of) x.y.z-SNAPSHOT
> 2) Commit pom version changes to the branch, tag as rc, and push
> 3) Perform testing and voting as necessary
> 3a) If the vote fails, make corrections and start over at 1)
> 4) After a vote passes, tag the release on the same commit that was the rc
> 5) Apply additional pom changes (i.e. increment to next SNAPSHOT version)
> 6) Create a new development branch x.y.a-SNAPSHOT based on the current tip
> of x.y.z-SNAPSHOT
> 7) Merge tag + version increment into x.y.a-SNAPSHOT branch
> 8) Delete all rc tags, rc branches, and x.y.z-SNAPSHOT
>
> After having typed that all out it kind of seems like a lot of steps to go
> through, but on the other hand, we're not going to be doing everything at
> once anyway.
>
> Additional feedback would be awesome.
>
> Mike
>