Shameless 'retweet' of Adrian's article announcing Aegir's move from CVS to Git for our development.

Those of you who have been cloning from my git repos at git.mig5.net, may now wish to clone from the officially-supported git repos at git.aegirproject.org. The Issue queues for reporting bugs will for the time being remain at d.o.

It's the million dollar question. And it's rarely been answered because it's so darn hard to do so.

Today I'd like to tell you how I do it with my favourite deployment weapons: Aegir, Version control, and Drush Make.

I thought I'd document the steps I did to set up a central git repository to which I can push to and pull from for various projects (including the Aegir components), as well as have the repositories sync from the CVS repository on drupal.org regularly.

Before I begin: I'm normally quite verbose and careful with my howtos. However, due to most unwelcome Nagios alerts at 3am on a Sunday morning, I've been awake for about 19 or 20 hours straight. Apologies for any errors with the following instructions, or steps I've missed :)

I've finally found some time to sort out my Git repos and get them together on one of my servers as a central location to pull from and push to.