I have a similar layout, and have decided to branch at the
product/common level.
Prod_a
Trunk
Branch
Tags
Prob_b
Trunk
Branck
Tags
Common
...
It just felt more natural to me. I then linked common into Prod_a,
Prod_b etc using externals, which are not without their own problems
when branching and tagging, but I can live with those problems. I am
new to Subversion myself, and someone on here advised me I was better
off the way Bryan suggested below - but I had already started down this
path to I going to stick with it for now, for better or for worse!
Stephen.
________________________________
From: Choate, Bryan (IHG) [mailto:Bryan.Choate@ichotelsgroup.com]
Sent: 09 January 2007 16:59
To: users@subversion.tigris.org
Subject: RE: Subversion Ideal repository layout
Vijay-
I have a similar situation, actually. I chose to stick to the model of
having top level branches, tags and trunk directories in the repository.
When checking out, developers can essentially cherry-pick the trees they
want to pull so you shouldn't be concerned with a file overhead
difference between the two, and there will be less effort involved on
your part in branching and tagging. That's just my personal preference,
though.
Hope this helps...
-Bryan
________________________________
From: Vijay.Nair@iflexsolutions.com
[mailto:Vijay.Nair@iflexsolutions.com]
Sent: Tuesday, January 09, 2007 6:53 AM
To: users@subversion.tigris.org
Subject: Subversion Ideal repository layout
Hello,
I am a new Subversion user and am going to raise a question which
probably has been answered umpteen times and I have seen a lot of best
practices out there too. But I still hope to receive less flame and some
practical answers about this
So here goes...
We are building a huge web application which essentially consists of
separate modules (lets say...Order Management System, Portfolio
Management System etc..). Each of these modules can be shipped
separately or as a single cohesive unit. Also these modules will be
built on a common set of frameworks (Logging, Security,
Transaction...the usual). The frameworks are also part of a single
module simply called the framework module
Should we go in for a one "trunk" - one "branch" (for releases) - one
"tags" folder for all the projects combined or for a one "trunk", one
"branch" and one "tag" folder structure per project. Would the release
cycle get cluttered in the second option which is of my opinion ?
Any answers would be greatly appreciated.
Thanks...Vijay
Received on Tue Jan 9 18:09:11 2007