I did a screencast on how you can use Drush Make to generate 'builds' based on Drupal core, with optional components such as install profiles + module/theme/library dependencies. The example given is the Managing News news aggregation system.

I then show how you can add the build as a Platform in Aegir, and rapidly provision sites on it in a multisite structure.

After noticing that in the community, some people are seeking a central community 'hub' Feature Server via which to upload and share their Features, I bought featureservers.org and set up http://community.featureservers.org to do exactly that.

Sorry, I couldn't resist :)

While I was writing my article on how to do deployments and workflow with Drush_make and Aegir, it occurred to me that once upon a time, I wrote an Installation Profile to build a Feature Server using the fserver feature itself, with the other required components such as Features, CCK, Views, etc per Development Seed's Recipé.

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.