We'd initially intended to take this opportunity to completely rewrite Aegir's codebase, however this has been postponed. For now, we are looking at doing a more-or-less straight port to Drupal 7. Our reasoning is that we need a stable D7 release by the time Drupal 8 is released, since D6 support won't extend much beyond that point. Considering the time-frame and available resources, we feel that a straight port to D7 will minimize risks, and give us the breathing room needed to undertake more significant architectural changes in the following release.
That said, we are still taking this opportunity to re-factor significant portions of the code-base. In addition, we have a number of new features and improvements that we'd like to see in Aegir 3. At this point, the scope remains somewhat fluid. We'll update this issue with additional details as they become more concrete.
We're intending tofor Aegir 3.0.0. This will allow us to have a "LTS" (long-term support) release in the 3.0.x series, but also allow us to add features, and make non-API-breaking changes in 3.x.0 releases.
We need to prioritize getting a stable 3.0.0 version released. To that end, we've begun tagging issues to allow us to help with that prioritization.
- Aegir 3.0.0: Immediate priorities blocking an initial release.
- Aegir 3.1.x: Feature additions and fixes that we'll want to prioritize next.
- Aegir 3.x.y: Anything else that we can likely fit into the Aegir 3 release cycle.
How can I get involved?
Help with any of the issues tagged for our initial 3.0.0 release is the priority.
We'll shortly be documenting a (relatively) simple way to test Aegir 3 and patches attached to our issues. In addition, we're shifting our documentation efforts to Aegir 3, which we'll be hosting on at: http://aegir.readthedocs.org/en/latest/index.html. These are both great ways for non-developers to help out.
In addition, you can have a look at the links to the issue queues for each of the components below. Find an issue that you like the look of and try to progress it a little, you don't have to complete the issue, you can just post a helpful comment, make a diagram, etc. You can chat with the Aegir maintainers via IRC if you need guidance on what issues to look at.
Donate Now to enable others to work more on this.
Provision's 7.x-3.x Issue Queue
Provision is independent of Drupal (since it's just Drush extensions) so there's little to do there directly related to the D7 port. However, this is where most of the heavy lifting in Aegir happens, so there are a number of issues we'd like to tackle in Aegir 3.
Eldir's 7.x-3.x Issue Queue
The theme has already been ported to D7, it's in the 7.x-3.x branch of the eldir project. See for more information. A UI refresh for Aegir 3 would be nice, but isn't currently a priority. If you're a UX enthusiast, we'd love to hear you ideas.
Hostmaster's 7.x-3.x Issue Queue
There is a port of the install profile in the 7.x-3.x branch of hostmaster. See for more information. While there isn't likely to be significant changes isolated to the installation profile, this is the queue used by the maintainers for issues that span multiple components.
Hosting's 7.x-3.x Issue Queue
This is the big one! This effort is progressing well: Aegir itself will install, and servers, platforms and sites can be created. We will soon undertake completing the D7 port of the non-core features. We are currently forward-porting much of the recent work that went into the Aegir 2 release. Much of what remains is Views integration fixes.