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

Huge repository

From: Zsolt <zkoppanylist_at_intland.com>
Date: 2006-08-21 14:16:13 CEST


One of our customers consider to use SVN to mange a large code (180 GB) for
a mid-medium size team. Few people with a lot of code, many variants from
the code for diiferent "product" variants. The commercial CMS tool providers
told us that this could be a problem for SVN.

Does anybody using SVN with >=180GB repository? Can SNV handle this
effectively for a team of 50 developers?

Another aspect where he needs more confidence in SVN is the question if SVN
supports a more stringent way to develop software. The ongoing development
process looks like this: Small team, lot of code, many internal
deliverables: some one checks out a file, does his work and checks-in again,
the release is managed by labels. Another project can now use this release
via a "use item". Typical question for him is: Is everything which was in
work already checked in.

Can SVN manage such process together with large repository?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 21 14:19:32 2006

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.