[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: Danny van Heumen <danny.vanheumen_at_hccnet.nl>
Date: 2007-01-10 12:45:28 CET


Srilakshmanan, Lakshman wrote:
>> I.e. if you have 2 projects that (maybe in the far future) need to
> work
>> together, you can create a branch with several projects.
> My understanding was that a branch reflects a project's development
> stream.
> What you are attempting to do is implement a development
> structure/dependency in a version control system.
Well, not exactly. I do think you should keep branches per project.
I.e. "/branch/project1/make-multi-processor". But this at least keeps
the possibility open if you need to branch multiple projects.

Like for example:
If you have a main application and some plugins for that application.
In general you could make the application and each plugin all separate
projects. But when you're going to make changes to the Plugin interface,
you would want to make a branch that covers all projects so you can make
all necessary changes at once.

> IMHO, your strategy will work, but I believe it could turn into a
> maintenance nightmare as each developer starts creating their own
> variation of branches containing combination of version from other
> projects, to make matters worse couple this with merging.
About the maintenance nightmare... I think that's a matter of creating
decent guidelines for the developers to follow. If you create
trunk/tags/branches folders per directory they're still just directories
and developers can still make a mess of it.



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 10 12:46:03 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.