Hello,
I would like to recommend subversion to my company, but there is one
feature subversion is currently lacking: the support for multiple
replicated repositories. The approaches known to me (svn::Mirror,
Svn::Push, svn-push) are not sufficient, because I need two way
synchronization. A maximum synchronization lag of 1-2 hours may be
acceptable. The revision numbers should be preserved across the
repositories. It should be possible to commit in the local repositories
even if the network links to the other repositories are down. The system
should support 10 or more connected repositories - I am thinking of a
hierarchical approach.
How many manmonths would it take to develop this sort of functionality?
My starting estimate is 3 months with a 4 developers to reach a state
where piloting is possible, and another 3 month with the same team to
reach production quality.
If this kind of feature was already discussed to death, please accept my
apologies. I couldn't find many references in the archive and the issue
tracker.
I also thought about a method to solve this problem.
Every connected repository would allocate an interval of revision
numbers, and use these numbers between synchronization runs. After the
synchronization, the repositories allocate a new interval (probably
including the unused revision numbers from the old interval). If the
intervals are large enough, even if the network links are down, commits
are still possible.
What do you think? If it's crap don't hesitate to tell me, so I don't
waste more time thinking about it.
Thanks,
Gergely
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 12 16:38:18 2004