Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <1325631276.22763.140661018896757@webmail.messagingengine.com>
References: 
 <CAJjMeYOegABL8FYWG1BkhGBE6vNXuWee0d-A_RdEP4Hk5K4oOw@mail.gmail.com>
	<1325631276.22763.140661018896757@webmail.messagingengine.com>
Date: Tue, 3 Jan 2012 21:07:23 -0600
Message-ID: 
 <CAJjMeYPQWg8zX54UuATSCW=fiGJPg_Z+CGwuzuCnpSxDuuYyQw@mail.gmail.com>
Subject: Re: Are you brave enough to manage a Subversion release?
From: Hyrum K Wright <hyrum.wright@wandisco.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: dev@subversion.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 3, 2012 at 4:54 PM, Daniel Shahaf <d.s@daniel.shahaf.name> wrot=
e:
> First of all, thanks for your tireless RM work over the last few years.

Thanks.  Although not without its headaches, I've gotten more out of
the experience than I have given.

> On Tue, Jan 3, 2012, at 16:11, Hyrum K Wright wrote:
>> written a lot of tooling and docs surrounding our release process.
>> I'd like to give somebody relatively unfamiliar with that environment
>> a chance to go through the process, to ensure all the required
>> information is properly recorded. =C2=A0I'm happy to do some handholding=
 as
> ...
>> responsiveness to the community, familiarity with the project
>> guidelines, and the ability and patience to herd cats / push string /
>
> Secondly, as you say, there are two separate parts to the RM role: one
> is the technical part --- creating tags, signing tarballs, sending
> release announcement emails --- but the other is the community part ---
> perhaps most obviously sending the periodical "Shall we roll a release
> next week?" mails.

Correct, and there's no inalterable law that dictates that these have
to be the same person.  Historically for Subversion they have been,
though, and given the size of our development community, I think it's
a good pattern to maintain.  (Although the technical bits can become
increasingly scripted.)

-Hyrum


--=20

uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com/