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

Re: Strategies for projects/branches layout

From: Tor Ringstad <tor.ringstad_at_tandberg.net>
Date: 2005-11-07 20:05:04 CET

> > [Jesse Erlbau]
> > Assume I have a repository which would house five related but
> > distinct development efforts. It seems I have to choose from the
> > start if I'm going to do:
> >
> > 1. .../repository/project/trunk/
> > 2. .../repository/trunk/project/

> [Ryan Schmidt]
> If the five development efforts are distinct, then you'll want to be
> able to branch and tag them separately, so your layout 1. above
> seems best

I'll argue that one a bit differently.

If your projects are truly distinct, it is not important which layout
you choose. You may find alternative 1) more logical, but even if you
choose 2), there's nothing that stops you from tagging and/or
branching at the project level.

On the other hand, if the projects are related in any way, chances are
that you'll sooner or later want to

- share code between projects,
- tag or branch across projects, or
- work with multiple projects in the same working copy.

If you choose layout 1), then you might be in trouble. The reasons
are that subversion doesn't work well across multiple working copies,
and the non-recursive checkout option is broken.

If these things matter to you, I'll recommend that you use layout 2)
unless you're absolutely sure your projects are distinct, and will
remain so in the future.

- Tor Ringstad -

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 7 20:12:47 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.