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

Re: What would be the best way to create "working repositories"?

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Tue, 29 Jun 2010 10:04:16 -0500

On 6/29/2010 8:39 AM, Tom Malia wrote:
> Completely understood and agreed.
> As I said, I was setting the stage, not dictating the absolute.
> I understood and agreed with Stephen's core points. I didn't find the
> approach to communicating those points particular efficient.

The first thing you need to consider is whether or not is is a good idea
to isolate your developers from each other. If you don't already have a
good spec with nailed down interfaces for components, you may just make
things worse when you try to merge the work done separately compared to
letting everyone update frequently to pick up others' changes on the
trunk and adapt as they go. Or if you do already have the interface
specs, maybe these separate components should be split into libraries
that could be completely isolated as different projects, perhaps even in
different repositories with the main program using external references
to pull them in. The latter approach might work if certain libraries
are permanently maintained by remote groups that want to have the
repository at their own locations. You could use svnsync to pull a
backup copy periodically if you want.

> My goal with the "over taxed" developers is explicitly to reduce that load.
> I am not necessarily "over taxed" and if necessary I'm looking for ways that
> I can take on as much of the burden of learning and possibly doing the
> processes necessary and only have to push as little as possible of that
> burden to the developers.

Subversion has a 'one central repository' model, so unless you can
completely split a project out to a different repository you would use
branches to isolate work. The git-svn suggestion permits something in
between where the remote developers would use git natively (probably no
harder than svn if you aren't already using one or the other) with the
git-svn program providing a link between their git work and the central
subversion repository so the changes could be pushed back only after the
work was complete. That is probably the closest you can get to your
initial request but as others have suggested, perhaps it really isn't
the best approach unless you have network connectivity issues that
interfere with using the central repository.

   Les Mikesell
Received on 2010-06-29 17:06:58 CEST

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.