[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: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2006-07-10 17:56:28 CEST

Malcolm Rowe wrote:
> On Mon, Jul 10, 2006 at 07:56:22AM -0700, Justin Erenkrantz wrote:
>>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
> +1.
> I also feel that we seem to be too hung up on creating a 'perfect'
> release. For example, we've had enough signatures for 1.4.0-rc1 to
> release for a while, but we held it up because of a theoretical problem
> that only manifested itself with BDB-backed --bdb-txn-nosync repositories.

Um. No. This was no theoretical problem. Tests were failing. Garrett and
I both experienced the problem independently. We held up the 1.4.0-rc1
release because we felt rc2 was gonna be out in a matter of days. In
retrospect, that might not have been such a good plan. Maybe better to
release rc1 with a warning message about known problems (I mean, I'm running
rc1 on svn.collab.net right now with no issues, so presumably others could,
too) and then continue as usual towards rc2.

C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on Mon Jul 10 17:57:00 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.