Good morning,
I have a question regarding maintaining multiple synchronized Subversion
repositories or in other words a Federated Repository
We have a distributed development team (one in Canada and another in
India), where each team has the ability to update and commit code to our
code repository. Subversion includes a number of benefits for minimizing
the amount of data being sent in / out of the repository on commits,
however due to the type of connection that our India team has (very slow
and unreliable) it makes sense to have a federated repository setup.
When I say federated repository, I mean that each team (Canada / India)
both have a working master copy of the repository of essentially the
same repository. Each team could treat their repository as a local
repository and check code into / out of the repository, thus mitigating
any WAN network issues since the repositories are essentially local to
that team. However, in this case Subversion would do all of the work in
keeping those two repositories in sync. There would be of course
situations where there would be conflicts on synchronization, but those
could be handled manually.
synsync is not a solution for this problem in that synsync creates
read-only mirrors and would not allow one of the teams to make commits
to their local repository.
Any direction or assistance on this would be greatly appreciated.
Steve Whatmore
Technical Lead Web Development
Sigma Software Solutions
55 York St., Suite 1100
Toronto, ON
M5J 1R7
Phone: 416.368.2000 x2293
Email: stevenw@sigmasoft.ca <mailto:stevenw@sigmasoft.ca>
MSN: steven.whatmore@hotmail.com <mailto:steven.whatmore@hotmail.com>
Web: www.sigmasoft.ca <http://www.sigmasoft.canorthplains.com/>
Skype: steven.whatmore <callto://steven.whatmore/>
Received on Fri Dec 15 15:28:30 2006