community.aegirproject.org

1.0 Release candidates

Updated by ldlts on 04/20/2012 - 17:51
AddedChangedDeleted

This section documents all the release candidates towards the 1.0 release.

1.0-rc7 release notes

Tagged:

The Aegir team is very pleased to announce the seventh release candidate of Aegir 1.0.

This release primarily fixes issues with our drush makefile which have prevented installations and upgrades of the last couple of releases. We have also fixed issues with the upgrade.sh script and the Debian packages.

1. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

Within those sections you'll find step-by-step instructions for performing both manual and automatic upgrade processes.

It is still imperative that you read the the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. This especially applies to users upgrading from before 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or recent rc releases, there are unlikely to be any version-specific manual steps required to upgrade, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

Back to top

2. 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 information: http://community.aegirproject.org/help

Thanks to our awesome community for their help, support and encouragement as always! Enjoy the new release :)

Back to top

3. Bugfixes

Back to top

4. Known issues

Back to top

1.0-rc6 release notes

Tagged:

The Aegir team is very pleased to announce the sixth release candidate of Aegir 1.0, aka "are we there yet?"

This is yet another hotfix release to fix an issue in the upgrade.sh script and Drupal 7 support.

1. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

Within those sections you'll find step-by-step instructions for performing both manual and automatic upgrade processes.

It is still imperative that you read the the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. This especially applies to users upgrading from before 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or rc1/2, there are unlikely to be any version-specific manual steps required to upgrade, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

Back to top

2. 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 information: http://community.aegirproject.org/help

Thanks to our awesome community for their help, support and encouragement as always! Enjoy the new release :)

Back to top

3. Known issues

The Debian package are still in testing mode and feedback there is appreciated.

Back to top

4. New features

We have now specific maintainers for specific project areas.

A documentation spree has been started by the newly documentation team and merged in this release, so the API documentation should be more complete. In particular, we have deprecated hosting_queues_get_arguments() and hook_provision_args() that weren't used anywhere.

Back to top

5. Bugfixes

Back to top

1.0-rc5 release notes

The Aegir team is very pleased to announce the fifth release candidate of Aegir 1.0!

This is a hotfix release to fix a major issue in the upgrade path. All users are strongly encouraged to skip the rc4 release and upgrade here instead.

Changes in 1.0-rc5

  • fix the upgrade path (#1118558)
  • fix upgrade.sh to have the right older version all the time and automatically detect drush (#1117776)

Known issues

  • Drupal 7 support is broken (hotfix available in #1119850)
  • upgrade.sh is broken again, use this version instead until rc6 comes out

This release is otherwise mostly identical to 1.0-rc4.

1.0-rc4 release notes

Tagged:

The Aegir team is very pleased to announce the fourth release candidate of Aegir 1.0!

We have again found critical issues in rc3, detailed below, and a few key features that we wanted to slip into 1.0 that were just low-hanging fruits that deserved to be released. We hope this release candidate will be all shiny and without any critical issues so we can release it as 1.0.

Update: because of a last minute API change, the upgrade path is broken and it is not recommended to upgrade to this release. A new release has been published, so use 1.0-rc5 instead. See #1118558 for more information.

Key changes in 1.0-rc4

  • There is now a ~/clients directory in which symlink are automatically created to allow easy access to all your client sites (#1115960)
  • A variable is now set in settings.php (aegir_api) to allow contrib modules to inspect what Aegir version they are dealing with, if any. The setting is removed on export, that is, if dbcloaking is off (#1027358)
  • We fixed a big regression where the mass migrate form stopped working in rc3 (#1111532)
  • The private directory of Drupal 7 is now properly protected (#1108810)
  • The Debian package has been tested over and over again and is now the prefered install method for people on Debian
  • Consequently, install.sh has been removed and the manual install instructions have been revamped to be clearer, see this post for more information about the reasoning behind that change

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)
  • Upgrade path is broken (#1118558)

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

In a similar fashion, the upgrade documentation has now been moved to the community site at

http://community.aegirproject.org/upgrading

Within those sections you'll find step-by-step instructions for performing both manual and automatic upgrade processes. You can download the upgrade.sh.txt script from http://community.aegirproject.org/node/431.

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 the 0.4 betas or rc1/2, there are unlikely to be any version-specific manual steps required to upgrade to 1.0-rc4, 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-6.x-1.0-rc3). If you are not, you may have to edit the script to change the OLD_DRUPAL_DIR variable.

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 information: http://community.aegirproject.org/help

Thanks to our awesome community for their help, support and encouragement as always! Enjoy the new release :)

New features

Bug fixes

1.0-rc3 release notes

Tagged:

Aegir 1.0-rc3 release notes

The Aegir team is very pleased to announce the third release candidate of Aegir 1.0!

This is the third Release Candidate from which we will test fixes to critical bugs from rc2, as well as fix any additional critical bugs found since, until we have no criticals and will then roll out the official 1.0.

This release also includes a fix for a security vulnerability (see below). We recommend you upgrade your Aegir instance to apply this fix.

Key changes in 1.0-rc3

  • A security vulnerability was fixed that prevents arbitrary configuration from being injected into Apache vhosts by way of the Site Aliases form. See #1098304

  • The 'Client' feature / node type has been significantly refactored and simplified, with the ultimate aim of hooking it into other CRM/databases (e.g. for LDAP support), and better Aegir-managed site/user security. This involved an exception to our current 'API freeze' for the sake of getting this important refactoring in. See this summary of the changes this imposes

  • We've upgraded to use Drush 4.4 and Drush Make 2.2 on fresh installs and upgrades. These have been tested and should work without any problems.

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)
  • The provision.info version tag wasn't updated properly and still reads 1.0-rc2
  • See all the issues tagged as aegir-1.0 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

In a similar fashion, the upgrade documentation has now been moved to the community site at

http://community.aegirproject.org/upgrading

Within those sections you'll find step-by-step instructions for performing both manual and automatic upgrade processes. You can download the upgrade.sh.txt script from http://community.aegirproject.org/node/431.

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 the 0.4 betas or rc1/2, there are unlikely to be any version-specific manual steps required to upgrade to 1.0-rc3, 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-6.x-1.0-rc2). If you are not, you may have to edit the script to change the OLD_DRUPAL_DIR variable.

Bugs fixed

New features

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! Enjoy the new release :)

1.0-rc2 release notes

The Aegir team is very pleased to announce the second release candidate of Aegir 1.0!

Yes, you read that right: 1.0! We've decided to rename the 0.4 branch to 1.0.

This is the second Release Candidate 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, we're back in the family!

We have fixed some key issues that were discovered during testing, including sites that were not put offline during migrations and data loss issues in multiserver migration. We have also worked on the upgrade path for legacy (pre alpha9) installs, which should be able to upgrade to this release directly.

Finally, we fixed a CSRF attack on the task form that allowed an attacker to force a user to run tasks on existing sites and platforms. This is non-critical as only tasks with no confirmation dialog (ie. safe tasks) could be triggered.

Also, we've moved to Drush Make 2.1!

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-1.0 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

In a similar fashion, the upgrade documentation has now been moved to the community site at

http://community.aegirproject.org/upgrading

Within those sections you'll find step-by-step instructions for performing both manual and automatic upgrade processes. You can download the upgrade.sh.txt script from http://community.aegirproject.org/node/431 (note, we point to the version in the 6.x-1.x branch because we accidentally rolled the tagged release before changing the AEGIR_VERSION number in the script. So use this version of the upgrade.sh script, or pay close attention to what version the script says it will upgrade to.)

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 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!

0.4-rc1 release notes

The Aegir team is very pleased to announce the first release candidate of Aegir 0.4!

This is the first rc from which we will go into crazy bugfixing mode until we have no criticals and will then roll out the official 0.4.

Key changes in 0.4-rc1

There are a lot of bug fixes and features added into this release.

Significantly, a major data-loss bug was fixed in Multiserver environments, that was causing a remote site's 'files' directory contents to be deleted if those files didn't already exist on the 'master' copy of the site on the hostmaster system.

Also, we stopped hardcoding "$conf['cache'] = 1" in sites' settings.php, returning control over the caching function back to the user by way of:

  • inserting the preferred setting into a file called 'local.settings.php' alongside the settings.php so it won't be clobbered by the template, or
  • same as above but in /var/aegir/config/includes/global.inc to set it globally for all sites, or
  • setting it in /admin/settings/performance on your site, and having that setting stick instead of being reset by the hardcode.

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 is as usual the excellent INSTALL.txt. The hostmaster and provision tarballs have the following checksums:

  • provision-0.4-rc1.tgz: 6f4da4ba7dcfaa1bcc3c44f96beb3eda
  • hostmaster-0.4-rc1.tgz: b2a42b151b817c1ea6cdf15462aa2e15

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-beta2 and earlier, we offer an upgrade.sh script in Provision, which tries to automate much of the steps outlined in the UPGRADE.txt.

It is still imperative that you read the UPGRADE.txt 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 or beta2, there are unlikely to be any version-specific manual steps required to upgrade to 0.4-rc1, 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-beta2). 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 or Drush Make 2.0?

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 or Drush Make 2.0.

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

Drush Make

Drush Make 2.0 has a bug that prevents building platforms from distributions that didn't come from drupal.org.

This has also been fixed in HEAD, but we are awaiting a 2.1 release before we roll with it. If you see 2.1 come out, you can probably upgrade your Drush Make if you wish.

See this ticket for more: http://drupal.org/node/1059238

We are working with the developers of these projects to attempt to 'sync' our releases in future, but we wanted to roll out rc1 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!