Release goals for 0.4

Now that 0.3 is out the door, it's time to sit down in a happy circle and decide what we're going to do with 0.4. We already have a draft in the 0.3 release notes but it's not a page everyone should be editing all the time. So here's a wiki page to do just that, bootstrapped with the list made up in the 0.3 release notes.

The official stated goal for this release, is that we wish to properly support 'multiple servers', and embrace the distributed nature of Aegir. The high priority features on that ever growing list are:

• multi-server support: the ability to easily manage sites running on as many servers as you need, with advanced configurations such as multiple web server front ends, load balancers, proxies and database servers
• site cloning support: The ability to duplicate an existing site exactly with a different url, as well as tracking multiple instances of sites (for example 'development', 'staging' and 'live' instances)
• Re-factoring the user interface: Improve the consistency and usability of the front end with the same razor focus we applied to our back end release.
• alias redirection: redirect www.example.com to example.com or foo.org
• various people will also be expanding Aegir with third party modules: DNS and Mail support, inter-site security, SSL support, a flexible quota system, features support, ...
• Perhaps a way to group sites together & share users/files/etc ... might be more easily handled by third party integration or one of the drupal contribs, could also be as simple as some doc instructions with various options, to start off simple! But wouldnt it be useful to facilitate this in the interface, not sure how messy this could be though!