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

RE: Subversion Ideal repository layout

From: Srilakshmanan, Lakshman <Lakshman.Srilakshmanan_at_tradingpost.com.au>
Date: 2007-01-10 00:15:55 CET

Hi Vija,


IMO, I would use the latter. I believe it is the natural way to
reference projects. For example if you need to find the status of a
project or need to view the log file for a project it could become quite
difficult following your first option.





From: Vijay.Nair@iflexsolutions.com
Sent: Tuesday, 9 January 2007 10:53 PM
To: users@subversion.tigris.org
Subject: Subversion Ideal repository layout




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.


Received on Wed Jan 10 00:16:59 2007

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.