Large development teams and SVN

A few questions on this topic:

1) What is the largest development team (executing actual commits, not counting read-only) that you had in one SVN repository? Did you have a problem?

2) Which largest group would be most convenient for you in one SVN repository? Is another version control tool better for very large teams? (Do not call IBM Rational because it will be ignored and flames, but others may be possible if a reasonable justification can be made. Mandatory compatibility with Solid Eclipse and Flex / Flash Builder is mandatory.)

2a) Obviously, this depends on the project, but are there any serious drawbacks associated with dividing the "large" development teams into small, modular teams , all of which use their own SVN repositions ?

3) Does it make sense for an organization to have two standard version control tools: one for large systems (if necessary) and one for small (~ 5 developers or less) systems?

For extra points:
4) What do you think is a “big” team (counting only developers , since this is related to the use of SVN, not QA, management, testers, etc.)?

+3
source share
2

1/ , 50-100 .
:

2/ VCS .
Perforce, .

2a/ , . , ( , ).

3/, , .

  • ( , , VCS, ).
  • VCS (freeware).

SVN , "" ( - , , ,... - , ).

4/ , ( ), 15 , , . , SVN-.

+3

SVN, , 80 000 CVS 3 .

, , SVN , ​​ . , , , .

+3

Source: https://habr.com/ru/post/1769477/


All Articles