Re: trunk/branches/tags and projects w/components

In this case you will want a global tags, branches, trunk. This way if you have a branch that modifies several subprojects, you can merge the changes to the trunk all together, instead of having to create multiple branches under each subproject and doing multiple merges later.

I also highly recommend trac if you're not already using it.

Russ
Sent wirelessly via BlackBerry from T-Mobile.

-----Original Message-----
From: "Walden H. Leverich" <WaldenL@techsoftinc.com>
Date: Wed, 11 Oct 2006 08:56:22
To:<users@subversion.tigris.org>
Subject: RE: trunk/branches/tags and projects w/components

>Do you want to have one branch in which you will change code for
>multiple projects (are the projects related?).

They're extremely related. Everything in this repository is part of a
single web-app. There is a "Site" folder which contains everything
needed in the website directory (.aspx, .jpg, .cfm, .css, etc.) And then
multiple folders for each of the site parts.

For example, there's a IRBGlobal project which contains nothing but the
global.asax file and the related c# code file. Only the .dll and .asax
file needs to go from here to the Site folder. There's a xForms project
that contains an entire subsystem of the site, but again only the .aspx
and .dll files make it into the Site directory.

The problem looking at is if I have a /trunk/Project<x> structure then I
branch way too much if I want to just make a branch of a subproject. But
if I go with a /Project<x>/trunk structure it's easy to end up with code
from /Project<y>/branch1 in /Project<x>/trunk since they don't branch
together, and it would be a killer to figure out which branch a file in
trunk came from.

-Walden

--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@TechSoftInc.com
http://www.TechSoftInc.com
Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
-----Original Message-----
From: Russ [mailto:rsivak@istandfor.com]
Sent: Tuesday, October 10, 2006 7:48 PM
To: Greg Thomas; Walden H. Leverich
Cc: users@subversion.tigris.org
Subject: Re: trunk/branches/tags and projects w/components
As mentioned, its really what suits you, but you should think about
branching.... Do you want to have one branch in which you will change
code for multiple projects (are the projects related?). If so, then you
probably want a too level tags, branches and trunk.  Otherwise you
should set up a too level folder for each project, and then have trunk,
tags and branches under each of the projects.  This way you are not
forced to checkout the whole project tree and switches and merges will
be faster.
Russ
Sent wirelessly via BlackBerry from T-Mobile.  
-----Original Message-----
From: Greg Thomas <thomasgd@omc.bt.co.uk>
Date: Tue, 10 Oct 2006 17:32:27
To:"Walden H. Leverich" <WaldenL@techsoftinc.com>
Cc:<users@subversion.tigris.org>
Subject:  Re: trunk/branches/tags and projects w/components
On Tue, 10 Oct 2006 12:22:08 -0400, "Walden H. Leverich"
<WaldenL@techsoftinc.com> wrote:
>In one case the trunk, branches and tags directories would be at the 
>top level, and all "sub-projects" would be w/in the top level trunk. In
>the other case the different sub-projects would be at the top level, 
>and each would have a trunk, branches and tags directory.
The answer is really whatever suits you. In my case, I have the
trunk/branch/tag under each project directory so I can easily control
access to each project.
Greg
--
This post represents the views of the author and does not necessarily
accurately represent the views of BT.
---------------------------------------------------------------------
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