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

Re: Merging the svndiff-patch branch to trunk

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2007-10-05 09:31:21 CEST

On 10/5/07, Ben Collins-Sussman <sussman@red-bean.com> wrote:
> Hm, I guess I disagree. 'svn patch' doesn't feel like a such a huge
> feature to me that it's worth holding back. If were half-implemented,
> sure, we wouldn't want to wait on it. But it's basically finished...
> it just needs some testing now, and I think it will (frankly) get a
> heck of a lot more testers attracted to it than merge-tracking.
> (Mainly because it's a much simpler, much more accessible new
> feature.)

Well, I'm for holding back. Myself, I have decided to set up branches
more frequently, in order to do work I want to be done. Then, when the
branch is done, we can move the work to trunk.

If we used that approach more, we could have a shorter release cycle
because new features are already waiting on a branch to be merged
right after the latest branches off for a release.

This way, right after a release we already have something new and
exciting for a new release... (Which should be an encouragement to
'not post-pone' as we have been doing with 1.5 when we started
merge-tracking. We already had releasable material when it started...)

Anyway, +1 to post-poning ctypes and svnpatch, to be merged to trunk
right after branching 1.5.



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 5 09:31:38 2007

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.