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

Re: named changesets

From: Johnathan Gifford <jgifford_at_wernervas.com>
Date: 2006-10-12 23:18:02 CEST

>>> On Thu, Oct 12, 2006 at 2:26 PM, in message
<20061012192644.GD7099@venus>, "Ed
S. Peschko" <esp5@pge.com> wrote:
> On Thu, Oct 12, 2006 at 09:40:12AM +0200, Ph. Marek wrote:
>> Hello Ed,
>> what you want are (maybe) branches.
>> Just create a branch with your specified name, switch to that
> commit,
>> switch back if needed.
>> If the feature is completed, do a "svn merge" of that branch.
>> Does that help?
> Yeah, it helps a bit, I guess - your idea is that we would have
implement one
> feature
> per branch, and then branch off of the branch in order to implement
> feature..

No, they are saying to create a branch from the trunk for each feature,
not off another branch. When a feature is ready, merge it back to
trunk. When you need to work on a new feature, crate another branch
from trunk.

> Am I understanding this right? The main problem with this is that we
> be
> branching *all the time*, and that we would have to branch in place
> our
> directory structure is tied to our environments, and those are
expensive to
> build.

Subverison uses cheap copies to create branches. Essentially, the file
in the branch is really a pointer to the original in the trunk until
that file is changed in the branch. So there is no expensive overhead
in Subversion for creating branches. As far as your systems, they
shouldn't know if they running a branch or the trunk as the file
structures under the branch should be identical to the trunk.

> I'd rather say that this particular branch contains independent
> 'a', 'b', and 'c', and that 'a' and 'b' are ready and can be merged,
but to
> hold off on 'c'.

If a, b, and c are contained in their own branch, that would be no
problem to do.

> Maybe though, its just my state of mind here...
> Ed
> To unsubscribe, e- mail: dev- unsubscribe@subversion.tigris.org
> For additional commands, e- mail: dev- help@subversion.tigris.org

Remember, Subversion is pretty dang flexible. You can take either a
stable trunk or unstable trunk approach. You can even do a combination
of both if your development team can keep it straight. While there are
recommendations to use tags, trunk, and branches, it's not a hard fast
rule or requirement in Subversion. A number of folks like using
'labels' rather than 'tags'.

Johnathan Gifford
Subversion Administrator
Werner Enterprises, Inc.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 12 23:18:50 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.