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

RE: Projects with subprojects

From: Bob Archer <bob.archer_at_amsi.com>
Date: Thu, 29 Oct 2009 10:29:08 -0400

> I'm currently working on a project made up of parts that could each be
> considered a project in itself. I plan on using redmine or trac to
> manage the project. Now I'm trying to figure out how to manage the
> repo(s) for the project.
> These are the current options I have in mind:
> 1. Create a separate repository for each sub-project and manage each
> separately in redmine (separate bug tracker, wiki, etc.)

I don't see a need to have separate repositories. Unless it is a requirement of the tracking software. Here was have three repositories only. Each is for a totally separate dev group that develop for totally different vertical markets. We use a very high level security... if you have access to the repo then you have full rights to it. So, seperating that at the repo level is just easier. I understand that path based authorization in svn slows the server down.

Having a single repository makes branching, externals and other stuff much easier.

> 2. Create a single repository with a subdirectory for each sub-project.

I lean towards this. You can go two ways with your folders too. You can have a single trunk/tag/branch hierarchy and each project within it. This would generally be used when all of the projects are versioned together. Or you could create a trunk/branch/tag hierarchy under each project folder. Or, you could do a hybrid of both. I suggest you read Chapter 5 of the svn book specifically http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.reposadmin.projects.chooselayout .



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-29 15:30:14 CET

This is an archived mail posted to the Subversion Users mailing list.