#vcs-shootout
http://wiki.mozilla.org/VersionControlSummit2006
http://wiki.mozilla.org/Version_Control_System_Requirements
http://bazaar-vcs.org/RcsComparisons

pains:
preed/bsmedberg get to rewrite client.mk
everyone gets to learn mercurial
for 1.9 we could also learn svn first

repository size jumps from 300m to 1g for mercurial

opensolaris and java and fedora extras are using mercurial
other projects are jumping to it
basically it seems like the momentum is to mercurial

concerned space / bandwidth:
l10n/modules/spidermonkey

dbaron is afraid of having major branches using different version control systems.

graydon/mkanat asked about bzr
 features: can do partial pulls and merges that cross renames
foreign branch support about mercurial

some webtools and doctools are using svn

git doesn't care about win32

subversion people promised some support for things
http://wiki.mozilla.org/Version_Control_System_Requirements/SVN_Responses

but brendan acknowledges that svn branching sucks as much as cvs

conversion time for mercurial is fairly fast. the concern is about community adoption. 

pavlov/vlad tried monotone

merge integration is mostly provided by:
meld xxdiff ediff/emerge tortoisemerge kdiff3

vlad says bzr's working model is too different
it does support partial pull, but no innertia, lack of performance (opensolaris dropped it)
used by cannonical
nobody spent much time with it

brendan: (consensus) is no need to go to svn on trunk

vlad: mercurial forest

possibly setup multiple repositories.

forking repositories is basically forbidden by cryptographic integrity

grouped commits affecting spidermonkey+dom

not moving trunk(mozilla1.9) to anything until (mercurial/bzr) mozilla2 is solved and happy

mercurial might eventually support partial checkouts 

mercurial doesn't handle to people doing directory renames in conflict
bzr handles this today

justdave: bzr allows for modules containing module lists

preed will contact mercurial  asking about our import/use plans

flock used mercurial and switched to svn (why?)
they might be considering switching back. why?

what follows is a channel log for posterity (chatzilla format)
http://viper.haque.net/~timeless/vcs.shootout.log