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

Re: Repository Layout Suggestions...?

From: William Nagel <bill_at_stagelogic.com>
Date: 2005-10-24 16:59:49 CEST

On Oct 24, 2005, at 9:38 AM, Dan Falconer wrote:

> I've got a project that's using SVN for it's versioning
> system. The project
> it's being used for is a website, whose code relies heavily upon a
> database
> for searching & authentication. Presently, for this project, we've
> got the
> standard "trunk/" and "branches/" directories, with only one
> directory under
> the "branches/" directory, called "dev" (where we keep all of the
> development
> changes).
> When we first started using a revisioning system (starting with
> CVS, then
> thankfully migrating to SVN), all of the development team worked on
> only one
> project, which was usually a short one, and then merged changes
> from the
> development branch ("branches/dev") into trunk. Now that we're
> working on
> multiple large projects, I'm not so sure that the current scheme is
> going to
> work.
> Given all that information, my question is this: what is the
> best way, in
> your experience(s), to determine what qualifies as needing it's own
> branch?

In my experience, any task large enough to require multiple commits
where the intermediate commits might break or otherwise interfere
with other unrelated development. In that case, the overhead of
doing merges will usually be outweighed by the reduction in
coordination necessary between developers.

> I was considering making a branch for each project, but that seems
> like a lot
> of potential merging that might not be needed.

It depends on how large/long-running your projects are. If the
projects are mostly short-running tasks that only require a few
commits and rarely run into conflict problems where one project
commit may break another project's work then "one branch per project"
may be overkill. On the other hand, if the projects are long-running
and large (which sounds like the case) then a branch for each project
may be a good idea. Actually if the project involves a lot of
developers over a long period of time you may even find it
advantageous to create branches of sub-projects within the larger


> Any and all comments will be
> appreciated. Thanks.
> - Dan Falconer
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 24 17:13:36 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.