[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: Daniel Berlin <dberlin_at_dberlin.org>
Date: 2006-07-10 00:48:15 CEST

Erik Huelsmann wrote:
> I'm not seeking to accuse anybody, but feel I should speak up about
> the way I'm feeling.
>
> Ever since 1.3, I feel like we're more and more unable to get releases
> out the door (within a reasonable time after branching).
>
> I haven't identified any reasons why this might be happening or even
> what to do about them. That is the reason of this mail: do others feel
> the same? Do you have ideas why it is happening? Do you have ideas how
> to prevent it?

I believe it is simply a matter of our release manager not having time.
Not that I blame him, it's just that we have no paid, full time release
manager, so we get releases when he has time to make them.

He hasn't had time lately due to other, higher priority (and rightly so)
commitments.

>
> One possible reason is that we have too many changes per release: most
> of which go largely untested as long as they're on trunk, getting
> first exposure on a release branch. When many changes/new features are
> exposed this way, stabilization takes a long time. This ofcourse isn't
> in any way 'the truth'. I hope others have thought about it too.

Sorry, I don't believe this at all. All the time we've spent has been
waiting for RC's to be rolled and getting signatures, not waiting for
features to be fixed.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 10 00:48:48 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.