DRAFT:: 1.0-rc2 release notes
The Aegir team is very pleased to announce the second release candidate of Aegir 1.0!
Note that we have decided to rename the 0.4 branch to 1.0.
This is the second rc from which we will test fixes to critical bugs from rc1, as well as fix any additional critical bugs found since, until we have no criticals and will then roll out the official 1.0.
Key changes in 1.0-rc2
There are a lot of bug fixes and features added into this release.
INSTALL.txt and UPGRADE.txt, along with the various architecture hints, and other developer docs, have been moved to the community site under:
http://community.aegirproject.org/administrator-manual
The Aegir git repositories have moved back to drupal.org
Known Issues
DNS has no access control - anybody can create any zone (#922252) The site form suffers from some performance issues when you have a lot of platforms (#955854) Cluster servers are probably broken right now (#1016890) Aliases are not persisted across Migrate, (Rename), Clone (provision-deploy) (#1004526) See all the issues tagged as aegir-0.4 and issues marked as 'major' for our comprehensive list of outstanding issues.
Installing and upgrading
The canonical source of installation documentation has moved from the usual INSTALL.txt to the community site at:
http://community.aegirproject.org/installing
The hostmaster and provision tarballs have the following checksums:
provision- hostmaster-
For users who have Rackspace Cloud accounts and want to install Aegir in the cloud, you are welcome to try mig5's Frigg script, which automatically creates a new virtual server and installs Aegir, with one command!
For users of 0.4-rc1 and earlier, we offer an upgrade.sh script in Provision, which tries to automate many of the steps outlined at:
http://community.aegirproject.org/upgrading
It is still imperative that you read the the Upgrade Guide (http://community.aegirproject.org/upgrading) and follow all version-specific upgrade instructions located at the end of the document before trying to run the upgrade script. This especially applies to users upgrading from before 0.4-alpha8, including 0.3.
For users coming from 0.4-beta1, beta2 or rc1, there are unlikely to be any version-specific manual steps required to upgrade to 1.0-rc2, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!
The upgrade.sh script attempts to backup the existing backend components, download new versions, and then run the hostmaster-migrate command. It assumes you are upgrading from the previous release (hostmaster-0.4-rc1). If you are not, you may have to edit the script to change the OLD_DRUPAL_DIR variable.
Bugs fixed
New features
No Drush 4?
Some people might be wondering why we haven't changed the install.sh or upgrade.sh scripts to fetch the latest Drush 4.2 release.
Drush
Drush 4.2 has a bug which breaks rsync and possibly other stuff when using multiserver.
It's been fixed in Drush, but we are awaiting a 4.3 release before we roll with it. If you see 4.3 come out, you can probably upgrade your Drush if you wish (we tested this morning and are in fact compatible with Drush HEAD at time of writing).
See this ticket for more: http://drupal.org/node/1041386
We are working with the Drush developers to attempt to 'sync' our releases in future, but we wanted to roll out rc2 to all you good folk sooner rather than later this time :)
Need help?
If you struggle to install or upgrade your Aegir system, you have a number of options available to you for getting help.
Consult this page for more: http://community.aegirproject.org/help
Thanks to our awesome community for their help, support and encouragement as always!