[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Our (in)ability to do releases?

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2006-07-10 16:56:22 CEST

On 7/10/06, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
> If nobody objects, I'd be willing to start picking up some of the RM
> tasks myself, I just don't want to step on anyones toes here.

As before, I'd be willing to be an RM for a 1.4.x RC as well.

I will reiterate that I dislike the fact that we have a concept of a
dedicated RM for all releases. This is not a new argument from me and
is not intended in any way towards our current RM. For those new to
SVN, I've made this argument for many years now as we've changed the
RM title (at least) three times now...

I really feel strongly that having a dedicated RM tends to stall the
process whenever that volunteer inevitably gets bogged down by Real
Life(tm). Other people then get in the mindset of "I can't do a
release without that one RM being available." That's just bad. The
RM title should only be given when that person says, "I'm going to do
1.4.0-RC1" - that should not mean that they are going to be RM for
1.4.0-RC2 or so forth...

The release process should be invokable and be able to be "run" by any
full SVN committer and not have to wait for any other person (except
for the 3 +1s to make the release public). It's not fair to the rest
of us who want to see releases out the door and have the time to help
out. -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 10 16:57:08 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.