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

Re: To Greg Stein

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Mon, 18 Aug 2008 08:41:36 -0400

Branko Čibej <brane_at_xbc.nu> writes:
> In general I dislike creating branches if the same work can be done on
> trunk without affecting the rest of the code. And I don't see a
> problem with including such work-in-progress code in a release.

I'm with Brane on this one. We haven't actually had a problem yet, and
IMHO it's unlikely that we will. The new wc-ng code is quite separate
from the old wc code. And there's nothing wrong with shipping a
work-in-progress, as long as it's clearly labeled as such: we did that
with serf for several releases, IIRC.

Regarding this:

> a) It will make the end result of your effort much easier to review.

With something like wc-ng, if we're not reviewing the commits as they
come in, then it's hopeless anyway :-). Once finished, a change like
that is much too big to review all at once. (But just to play the other
side: the bulk of the work is going into new files anyway, so if one
wanted to review the "state of wc-ng" at any point, one would just look
at those files. This will remain true until the work starts touching
libsvn_client, and at that point, I'd much rather have it in trunk so we
can keep the changes closely coordinated with old libsvn_wc maintenance.)

Let's please go with trunk until there's actually a problem. We can
make a branch at any time if we need to.


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-08-18 14:41:58 CEST

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.