[Adium-devl] Let's switch to a DVCS

[Peter Hosey]

On 2009-04-14, at 20:17, David Smith wrote:
> As I understand it we've been waiting for Augie's work on  
> hgsubversion to mature. Our svn repo is... odd, and breaks most tools.

hg convert worked somewhat well the last time I tried it. The biggest  
problem I remember is that it operated in fits, running out of memory  
every few thousand commits. hgsubversion does this, too; it may be  
unavoidable. (If we had better Python memory-profiling tools, we could  
work on this; as it is, any attempt to optimize the memory usage of a  
Python program relies on guesswork at best.)

hg convert might have had another problem, but if it did, I don't  
remember it. The only thing I remember is the running-out-of-memory  
problem.

I tried to use hgsubversion on the Adium repo today, actually, and got  
pretty far, but it choked shortly after r24000:

	<https://bitbucket.org/durin42/hgsubversion/issue/73/assertion-failure-when-pulling 
 >

So, what do you think? Try hg convert again, or wait for hgsubversion?

My current criteria for a tool to pass:

1. Every active branch can build a release. (Proves that at least the  
current source is consistent.)
2. No false branches or tags. (Proves that the converter is not making  
things up.)
3. No branches become tags, nor tags become branches. (Proves that the  
converter has guessed correctly all branch and tag operations to date.)

When we're ready to make the switch, we can turn off the Subversion  
server, dump the Subversion repo into a bzip2'd dump file, and clone a  
Mercurial repo up to the server and serve it with hgweb and ssh.