You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Walden H. Leverich" <Wa...@techsoftinc.com> on 2006/10/10 16:22:08 UTC
trunk/branches/tags and projects w/components
I've got a "best practices" question...
I'm trying to decide between two layouts for a project w/in subversion.
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. There's a
directory example below.
The subprojects have components which end up in the /Site project.
Basically the subprojects are ASP.NET projects where the /Site directory
is the actual website. We only put the .aspx and .dll files in the /Site
project and keep the .cs and other supporting files in each of the
individual project directories.
I can come up with arguments for both approaches (and a hybrid of
projects in /trunk, branches and tags and then each projects also having
/trunk, branches and tags) so I'm looking for a "best practices" answer
of how this should be done.
Ideas?
-Walden
Example:
/Repository
/trunk
/Site
/Reports
/Forms
/branches
/...
/tags
/...
vs.
/Repository
/Site
/trunk
/branches
/tags
/Reports
/trunk
/branches
/tags
/Forms
/trunk
/branches
/tag
etc.
--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@TechSoftInc.com
http://www.TechSoftInc.com
<blocked::blocked::http://www.techsoftinc.com/>
Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
Re: trunk/branches/tags and projects w/components
Posted by Russ <rs...@istandfor.com>.
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 <th...@omc.bt.co.uk>
Date: Tue, 10 Oct 2006 17:32:27
To:"Walden H. Leverich" <Wa...@techsoftinc.com>
Cc:<us...@subversion.tigris.org>
Subject: Re: trunk/branches/tags and projects w/components
On Tue, 10 Oct 2006 12:22:08 -0400, "Walden H. Leverich"
<Wa...@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
Re: trunk/branches/tags and projects w/components
Posted by Greg Thomas <th...@omc.bt.co.uk>.
On Tue, 10 Oct 2006 12:22:08 -0400, "Walden H. Leverich"
<Wa...@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