Hi Danny,
> 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.
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.
Thanks
Lakshman
> -----Original Message-----
> From: Danny van Heumen [mailto:danny.vanheumen@hccnet.nl]
> Sent: Wednesday, 10 January 2007 11:23 AM
> To: Vijay.Nair@iflexsolutions.com
> Cc: users@subversion.tigris.org
> Subject: Re: Subversion Ideal repository layout
>
> Hi,
>
> I would suggest separating trunk, tags and branches first.
>
> /trunk
> /project1
> /project2
> /tags
> /project1
> /project2
> /branches
> /project1
> /project2
>
>
> In think the most important difference is that this allows for related
> projects to interact.
> 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.
> Would you choose to create trunk, tags, branches per directory, you
> can't just select the projects to branch. You would need to choose a
> branch-location on either of the related project's branch directories.
>
>
> I hope I made myself clear?! :P
>
> Danny
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 10 02:24:18 2007