Me and antoine were discussing, and we're at a point where we REALLY have to look to find bugs in the alpha. We feel that the new features are more than adequate to make a proper release, so we've decided to basically go into a pseudo feature freeze.
We're going to look into adding http://drupal.org/node/371769 and possibly http://drupal.org/node/337485 still, but out main objective is to get a drush 2.x final release out as soon as humanly possible (it's the only real thing blocking release at the moment)
The very first objective once we have a 0.2 release, is to upgrade the front end to Drupal 6, which will then open an entire avenue of related user interface improvements we already have planned, and also open the door to fixing some of the biggest issues we have for 0.3 (almost all of which are user interface related), in a much timelier fashion.
The move to Drupal 6 will reduce a bunch of kludges we have on the front end, such as the custom install wizard api i wrote, and will likely reduce a significant amount of code too. We also open the door to replacing our custom listing code, with complete views 2 support. We dropped views 1 support during the 0.1 development cycle because we couldn't afford the time investment to support it fully and then re-write all the views integration code for the very next release.
If you want to help get this release of Aegir out and allow us to focus on bigger and better things, now is the time to get involved. Start testing Drush 2.x and get involved in the issue queues, Download and install Aegir for yourself and help us find any bugs.
Onward and upward.