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

[Peter Hosey]

On 2009-04-15, at 16:02, Zachary West wrote:
> Also, just throwing it out there, but there's no reason we couldn't  
> look at other locations for hosting the repository. Something like  
> bitbucket (how's that working for growl?) might be a good option.

It's mainly an artifact out of my earlier plan for a more distributed  
workflow.

I converted our (Growl's) repo with full history, which makes it about  
70 MiB. Anyone who has two of these will be pushing the limits of the  
free Bitbucket account tier. The Adium repo will need to get under 150  
MiB to fit even once, and that's assuming that we stop adding commits  
to do it.

hgweb works really well. Behold:

	http://growl.info/hg/growl-development
	http://growl.info/hg/growl-development/graph

We're using SSH for pushing. Every developer has an account that only  
works for hg operations, using their public and private keys to  
authenticate the connection.

Adium can continue using Trac for tickets and wiki pages.

> We could separate out the development-end tickets and the user-end  
> tickets, which might be a plus too.

Yeah, every Bitbucket repo comes with an issue tracker. Our  
recommended practice on Growl  (well, mine, at least—not sure whether  
I wrote it down anywhere as official policy) is to use these for bugs  
relating to feature branches (e.g., you would file GNTP-related bugs  
on Evan's bug tracker, at least until we end the branch by merging it  
into the default branch), and our Launchpad tracker for bugs in the  
main Growl source.