Norbert Unterberg wrote:
> Ben Collins-Sussman schrieb:
>> Case Study: the Mono project adopts Subversion
> 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
> 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...
I gave a presentation on "Subversion Best Practices" at OSCON this year,
and you can see the slides on my web site at:
There's also a chapter about the same topic, covering some of the same
things in more depth, in my book "Practical Subversion", which came out
this week and is available on Amazon.
Some of the same topics are covered in the other svn book, but there's
no specific section on it that I can find.
Ben also wrote some stuff on the subject, which is available at:
I hope this helps,
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Nov 17 21:31:44 2004