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

RE: RE: Re: Multiple vs Single Repositories

From: Irvine, Chuck R [EQ] <Chuck.R.Irvine_at_Embarq.com>
Date: 2007-05-02 21:22:17 CEST

> >
> Andreas has some good advise already re: single vs. multiple,
> espcially in the repo hook files.
> If you elect for a single repo, how about this structure?
> Repo/
> trunk/
> app1
> app2
> ...
> branches/
> some_branch/
> tags/
> some_tag/
> This way you can branch/tag all your apps; e.g., you can tag
> all of the R1, R2, R3 for releases.

This wouldn't work for us. App1, app2, etc. aren't components of the
same application. They are truly different applications with different
release schedules and they each have their own set of trunk/branches.
Also, completely separate teams development the different apps. So, for
authorization purposes,


Works better.

Actually, though, it's not the repo layout that is our concern in this
instance. Our concern is whether we should have separate repos to limit
the scope of outage and effect in case of a repo corruption.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 2 21:22:42 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.