1.0 release coordination

I believe we are ready for 1.0. There are no critical bugs in the queue and jenkins is green.

We need to build release nodes and noise around this release. It would be nice if we could have a general overview of the work we did in the last what... two years now?! Aegir evolved a *lot* since our "last stable release" (0.3 officially) and it would be important to reflect that.

That could also serve as a product description in the documentation, outlining the major features and shortcomings of Aegir.

My dream would be to see all the release notes squashed into a single one... that's 24 release notes. :) Maybe we don't need all the bug list, but the "major changes" list could be used in a significant way...

I would also like to see some work of people going over the list of major bugs and document those as known issues (well not necessarily *all* of them, but you get the idea)...

The release notes should also outline the 2.0 roadmap and how we were still pretty successful in completing the 1.0 roadmap, even if it took a while, with only poor DNS stuck in the unclosed 1.0 issues.

Ah, and we should plan the 1.x branch release cycle too.. My idea was to keep the branch still a bit open to document changes and small non-invasive fixes like performance issues, major or "aegirWTF" issues.. API changes are a no-no of course, unless they are additions *and* are tested in the 2.x first.

What else would we need... how about having a release party? :)