On Nov 17, 2004, at 11:16 AM, Ben Collins-Sussman wrote:
>
> Case Study: the Mono project adopts Subversion
> ===============================================
>
>
-- UPDATE --
Clarifications from Miguel de Icaza, after reading this paper:
* A big reason for switching to Subversion was for renames/copies.
They've been dying for that. They're tired of breaking their CVS
repository doing 'surgery' on it to move files, things
disappearing, reappearing, etc. They also want to re-org
directories.
* The main motivation for maintaining 'Changelog' is because it ends
up in the final tarball release, distributed to the general
public. That makes a lot of sense; we have our own CHANGES file
that we write just before each release, which is just an edited,
simplified summary of the output of 'svn log'. We do ours just
before release, they do theirs as they go. The amount of work is
the same, though data is being duplicated in the Mono case. Not a
horrible thing.
* Mono *did* do some preliminary Subversion testing with smaller
sub-projects (MonoDevelop and Msbuild), so there was some
familiarity. But the projects were much smaller than Mono itself,
so the 'svn blame' speed issue wasn't noticeable on files with
little history.
---------------------------------------------------------------------
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:24:33 2004