Ben Collins-Sussman schrieb:
> Case Study: the Mono project adopts Subversion
> ===============================================
Ben,
I would find it very helpful for many developers/project teams if you
put something like this case study (or at least the conclusions) into
some white paper on the web site. Maybe a compressed "Switching to
Subversion" guide that covers techial as well as non-techical aspects of
such a conversion (like line-ending problems, changelog, space and speed
considerations etc). That might help people evaluate the possible
impacts that a switch to subversion might have on their projets and
procedures.
In addition, do you know links to "SCM best practices" documents that
you can recomend? If not, how about writing or developing such a
document? I work in a team in our company using CVS, and I would like to
switch to subversion (because of I think CVS lacks most: The project
wide log). But in respect to SCMs best practices, I feel our team is
still in some kind of beginner's position. It would be very helpful to
learn something about SCM which goes beyond svn command line syntax and
basic repository layout.
I know you answer might be "A patch would be welcome", but since I still
feel not very experienced in SCMs I would obviously be the wrong person
to ask...
Keep on the good work!
Norbert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 17 21:25:00 2004