Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of ben@reser.org designates
 50.197.89.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <51DDE084.3020505@apache.org>
References: <20130710014107.38de654a@hub>
	<CALK=YjN51gLj-N2TxtkcWBjWdqzBneEpPzECi4-u8Y+tT=QPSA@mail.gmail.com>
	<8253AC22-B52B-425E-A552-1B631014EA98@jaguNET.com>
	<51DDE084.3020505@apache.org>
Date: Wed, 10 Jul 2013 16:33:15 -0700
Message-ID: 
 <CADkdwvQKA=8afvR=d2U6wke6T01Pi6eJxaibhXx6bva0yXbipw@mail.gmail.com>
Subject: Re: [VOTE] The 'RM' Baton
From: Ben Reser <ben@reser.org>
To: dev <dev@httpd.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jul 10, 2013 at 3:30 PM, Guenter Knauf <fuankg@apache.org> wrote:
> I was also thinking about learning how to release - but the lack of proper
> documentation for the whole process holds me back; I remember how Graham
> fell from one trap into another when he did his 1st APR release, and I dont
> want to get same ...
> so, if we want to have more folks doing more frequently releases the
> startpoint would be to 1st document how a release is done:
> - required auto* tools versions
> - step by step description how to prepare for a release

You guys may want to look at our release process over at the Subversion project:
http://subversion.apache.org/docs/community-guide/releasing.html#release-creating

We also have it somewhat automated.  Including getting the right auto*
tools versions.  Of particular interest might be our release.py tool:
http://svn.apache.org/repos/asf/subversion/trunk/tools/dist/release.py

For actually rolling that python script ends up driving this shell
script that I wrote long before the python script was developed:
http://svn.apache.org/repos/asf/subversion/trunk/tools/dist/dist.sh

All of this is obviously under ASLv2 so feel free to borrow and adapt. :)