Re: Parallel branches/tags/trunk directories

> I'll bite...
> Why do you need to checkout everything from the "proj" level of the
> tree? If it is common to checkout from the project level of the tree,
> how do you branch or tag if you have to branch and tag each and every
> directory?

Sorry, I missed this earlier reply.  You identify good issues, David, and I've raised them.  I think it's one of those things where I can see the issues before others do, and until the pain becomes theirs personally, there's no point in trying.

> proj/trunk|tags|branches/*

I've used that project layout in all my past projects with SVN, CVS, ... sccs (yes, way back).  In this particular project, the sets of deploy/ directories will be managed separately by another team.

My attempt at anonymization unfortunately obfuscated the layout a bit.  I can see reasons for a layout like this in our case:

proj/common/trunk|tags|branches
proj/top[1|2]/trunk|tags|branchesproj/deploy/common/trunk|tags|branches

proj/deploy/top[1|2]/trunk|tags|branches/env[1-9]
The codebase resides in the first trees, and runtime configuration (deploy) stuff in the latter ones.  The top1/ and top2/ projects evolve independently, but share the common/ stuff.

I agree that SVN makes adjusting this pretty simple.  I hope we have that opportunity before the concrete hardens too much more.  Thanks.
Received on 2011-08-12 03:13:22 CEST