community.aegirproject.org

anarcat's picture
anarcat
8:12pm Sep 18, 2012

Another stab at the short and long term roadmap for Aegir 2.x and 3.x

The Aegir core team has taken some time to reflect upon the progress of the upcoming 2.x release, along with the longer roadmap for what we are starting to call 3.x. This is a product of discussions about the 2.x release schedule prior to Munich and an informal chat on september 10th after DC Munich. You may also have seen this transpired through one of the three Aegir sessions at Drupalcon Munich.

Here I will try to summarize those discussions in a comprehensible whole.

Some general thoughts

  • we wish to make major releases more often - 1.x is getting old, and we are being forced to merge down new cool functionality from the 2.x branch down into 1.x as we go along
  • we are still postponing the Drupal 7 port of the frontend to after 2.x
  • we have discussed moving roadmap planning to Koumbit's Redmine (or another Redmine instance), but discarded the idea because of the barrier of entry (you need to register and be approved so that spam is controled). Instead, we'll make clever use of tags and the handbook.
  • there was the idea of alternating backend and frontend freezes between releases, this is still being discussed

2.x release schedule

We have announced a release schedule at Munich. We have also settled on a smaller feature set to make sure we meet that schedule.

Prior art:

We have set the following priorities:

  1. subsite support (#705026) - now that mig5 did most of the work ;)
  2. nginx cleanup (#1635596, #1635622, #1622846, #1635586, #1608910) and Nginx Debian package (#1348560)
  3. files/ sync settled (#1083366)
  4. SSL code cleanup (#941870, see also this report)

We would like to get those in 2.x, but we are not fooling ourselves: if nobody finds the time, they will be postponed to 3.x.

  1. standard archive support (#1138882, original roadmap description)
  2. intersite security (the infamous #762138)
  3. more intelligence in spokes (original roadmap description)

We are aiming for the following schedule:

  • alpha/beta release by end of september
  • rcs by october
  • release planned on october 31th

3.x release goals and schedule

We're looking at releasing 3.x in 2013, before D8 is stable and D6 support is dropped. Of course, we will keep on supporting installing D6, D7 and D8 sites throughout this time.

Those are the broad release objectives we have fixed:

  • full rewrite in D7
  • make more use of 'standard' Drupal contrib modules:
    • drop custom listings in favor of real views, VBO
    • drop clients in favor of OG
  • move stuff to contrib (DNS, etc)