Comments on: What’s your favorite Subversion repository organization scheme?

By: Dan Skaggs

Dan Skaggs — Tue, 19 May 2009 00:40:02 +0000

@Mark…That’s an interesting method. It’s kind of a half-way point between the two schemes that I had outline. I have several different clients each with 1-5 projects so that makes for a pretty good number of subversion repositories set up in Subclipse. With your method, I could still keep things organized but reduce the number of repositories necessary.

@Jim I’ve been operating under 1 repo per project now too. I’d not thought about the “going wrong” part of the repo. As important as it is to have a good backup scheme, I could see where it would be even more important to have an airtight backup scheme with the one master repo scheme.

@Michael Thanks for the recommendation. I’ll definitely check that out.

By: Michael Henke

Michael Henke — Mon, 18 May 2009 04:02:58 +0000

checkout this book for some subversion setup case studies http://tinyurl.com/oanvgx

By: Jim Priest

Jim Priest — Mon, 18 May 2009 01:38:28 +0000

I’ve always been a fan of one project per repository. My big fear of multiple projects in one repo is if anything goes wrong – it goes wrong for everything :)

That said we’re using JIRA now and slowly moving to one massive repo so the pointy-hair management people can pull useful info out of JIRA/SVN.

By: Mark Jones

Mark Jones — Mon, 18 May 2009 00:06:01 +0000

I handle multiple clients at my job, so we do a little of both; every client has their own repository with all their projects sharing it. This way we can move each client’s repo somewhere else (or hand it over to the client) without having to hand over other clients’ data.

We don’t currently integrate with external apps like Trac though, so if there’s a reason to split every project into its own repo, I don’t see the harm of it. it’ll help keep the individual repo sizes as small as possible, which could be useful if you need to move / split things up ever.