[meta] Roadmap: Aegir 3.x (D7 port)

Thanks for writing this up!

Just thinking out loud, but does it make sense to have a 7.x-1.x branch, that has feature parity with 6.x-1.x and is basically a straight port? 7.x-2.x then becomes the new hotness afterwards.

I am not sure we have the manpower to maintain 3 branches at a time. I would rather keep D7 as one of the features of 2.x than try to push three release branches at the same time...

Anyways, as things stand now, 2.x is pretty close to 1.x in terms of features and if we concentrate on the D7 port, I feel that is pretty much what it's going to be. :)

We could, however, have a feature branch for D7... but I would try to merge it in as soon as it's functional. Same for Drush 5 support, btw.

I'm going to port Eldir!

So I've worked on a 'harness' for porting Eldir (will open a different issue for that) that is basically a D7 implementation of the main tables and forms in Aegir, you can build it using the stub here:

http://drupal.org/sandbox/darthsteven/1267494

I've made the 7.x-2.x branch actually use Drupal 7, which means that branch is totally broken now, but there's a 6.x-2.x for those that want new stuff, but not Drupal 7. It just makes more sense that way.

The Eldir theme has been ported and committed to Hostmaster 7.x-2.x.

Subscribing.

Me too ))

subscribe
#spam

@skwashd - you can follow issues now, no need to subscribe anymore! sorry for the spam.

Changing title to reflect what we're actually going to do, and assigning it to me so it's clear that I have ownership of this initiative.

updated with the issues I've created

Update the summary to indicate that we are doing a rewrite, not a port.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

So we pretty much decided over on the community site to put the D7 port on hold, and do a D8 port instead!

Updated issue summary.

Er, okay, I'm glad this discussion happened where people could actually see it and participate.

I'd really love to have the frontend of Aegir implemented in Drupal 7, using entities and fields etc. But it's a massive task to re-write Aegir, in fact I'm not sure we'll be able to complete until summer 2013, which is when D8 is supposed to be release. So at that point, do we just port to D8 (hopefully a lot less painful)?
It seems that porting to D7 is splitting our focus and resources maybe, if we switched to just saying, new features go into 6.x-2.x, and we just have a good year or so of building on Aegir and making it better and more refined. We can use the time to clean up 6.x-2.x and make the code base cleaner and organised better etc.
Then at some point, when D8 hits feature freeze we start building the frontend on top of D8, and after it comes out we release too.

This is madness. Think about this timeline a bit more: D6 will be EOL and unsupported by the time Aegir is released on top of Drupal 8. Most of the things that we'd have to do for a D8 rewrite are nearly identical for what we'd have to do for a D7 rewrite (converting some things to Entities, cleaning up the code, perhaps replacing all the hardcoded lists with Views, etc). Telling people that they have to install a really old version of Drupal just to run Aegir just won't do. I really hate that I have to run Drupal 6 to be able to use Aegir, and I suspect that there are some other people in that boat as well.

If you guys don't want to rewrite the frontend on Drupal 7, then fine. But don't completely discard the idea of a D7 port - it's still important, even if it's a lot of work. I don't think it will be that bad and I'd be happy to look at certain components over the next few months. Worst case, I'll try to gather up some funding to get a developer paid to do the upgrade.

Hell, if you would have announced this a week ago, I would have submitted a GSoC project for it >.<

This is marked postponed (clarified the status while I'm here), which means anyone is free to pick this up and run. Code is gold.

We, on the other hand, have plenty of other stuff on our hands to run with, so we're focusing on what seems really important right now.

Note that you usually don't "install drupal" yourself to run aegir, it installs it for you, and in a dedicated platform anyways, so I don't see this as being so much of an issue.

This is marked postponed (clarified the status while I'm here), which means anyone is free to pick this up and run. Code is gold.
We, on the other hand, have plenty of other stuff on our hands to run with, so we're focusing on what seems really important right now.

Sure, I can understand prioritization, but throwing out the D7 port just seems silly. Most of the things that will have to be done for a D8 port will also have to be done for a D7 port. IMO, doing the D7 port helps to line the system up for an easy-ish D8 port.

Note that you usually don't "install drupal" yourself to run aegir, it installs it for you, and in a dedicated platform anyways, so I don't see this as being so much of an issue.

I'm aware of that, but the fact that I have a Drupal 6 installation sitting around drives me nuts. I won't even install Open Atrium anymore because of that reason.

This just in:
http://drupal.org/project/dns
Module to help administer your DNS records in Drupal. Will be built for Drupal 7 using the new entity system.

What is the status on this project? It seems the aegir community is hard at work moving towards d7 but this thread seems to indicate the next drupal ready aegir platform will be for d8?

As far as I know, no one is working on the D7 rewrite.

I started on it, but have been slammed lately, so I haven't been able to work on it as much as I'd have liked.

Awesome news! Please consider publishing your work to a sandbox so that it is not lost if you stop again. :) Are you starting from the current d7 rewrite branch (7.x-2.x)?

Updated issue summary.

mention the straight port

clarify status of eldir and other things

Just to clarify the current situation: we are *not* giving up on the port to D7. If someone wants to rush this for Aegir 2, it would even be welcome, but I am doubtful that a port would be possible by the time we want to release 2.x (that is: real soon now).

We are not going to do the full entities port however - we will just do a minimal port to ensure continuity and keep the rewrite for an eventual D8 port, in Aegir 3 or 4.

So ideally, Aegir 2 would be Drupal 7 and Aegir 3 Drupal 8, but we don't want to wait that long to release Aegir 2, so it's mostl likely going to be:

• Aegir 2: Drupal 6, short-lived
• Aegir 3: Drupal 7, trivial port
• Aegir 4: Drupal 8, rewrite with entities and so on

So while I think that adding Selenium tests for the full Aegir stack is a good idea, I wonder if we could add normal Drupal simpletests and get it working somehow.

@anarcat
will our installs be able to upgrade from 1.x to 3.x and bypass 2.x?

@marafa - usually not. Aegir is designed to be upgraded to skip minor but not major versions.

clarify the status of everything

Lets discuss how we merge code from 6.x-2.x to 7.x-3.x...

Ideal would be to only work on 3.x and backport important fixes... but work on 2.x is still ongoing to get it stable.

I'd hate to lose work.
@Steven Jones or @ergonlogic: would you be willing to merge in the recent 2.x commits for the time being? Or should the committer be responsible to get it it 3.x?

Can't we just git merge the trees?

Aka git co 7.x-3.x ; git merge 6.x-2.x?

Setting the correct version.

I guess we would also want to consider support for Drush 8.x-6.x as that is in beta now

adding tag to be able to hunt down other similar issues.

alright, i got rid of all the other instances of that tag - we should now use 7.x-3.x-dev for all 3.x issues.

I've opened an extra meta issue to discuss Drush 6: #2002804: [meta] depend on Drush 8.x-6.x?

Hi all, just chiming in here to get an idea of what the plan is for this? From the issue summary it seems like you've halted work until D8 for the port? Or are you going to proceed with this D7 port as well as the D8 port down the road?

Cheers

@acbramley, work is ongoing. See http://drupalcode.org/project/hosting.git/tree/refs/heads/7.x-3.x and http://drupalcode.org/project/provision.git/tree/refs/heads/7.x-3.x

added extra task

Thanks a lot for the issue summary update, makes it a lot clearer :)

Updated issue summary.

I suggest going through each of the subprojects and creating a meta issue for each one that lists all of the issues required for a 7.x-3.0 release, that'd help focus the community towards getting the release out the door.

i believe there are issues with the upgrade path. from 2.x to 2.x+1. has this been fixed in 3.x? if not shouldnt it have its own meta issue? #2181885 #2197443 etc?

also curious how production sites upgrade their installation base. or do they?

I've created #2262575: [meta] Upgrade path Aegir 2.x to 3.x for this. Feel free to add...

PS: @marafa: if you add [# and ] around the issue numbers they get rendered as a link... #2181885: upgrade script should handle config move too #2197443: upgrade.sh script doesnt update drush installed via pear

Updated the links in the description (the Hostmaster is now titled Hostmaster (Aegir)).

Also it seems we need to tag more issues, as there are only 2 tagged as 3.0.0

I'd like to get out an alpha release before DrupalCon Amsterdam. Then we can work towards a beta during and after

Any alpha blockers?

Maybe #2300537: Merge Provision extensions into Hosting modules

We have an alpha: http://community.aegirproject.org/3.0-alpha1

Alpha2: http://community.aegirproject.org/3.0-alpha2

I've added a number of issues to the Aegir 3.0.0 tag.

I'm not sure all of them should be release blockers, but it's a start to get to a release...

Although I can't be there the Global Sprint Weekend might inspire some....

As the recent testbot failures have been fixed we should be ready for a new beta release ....

beta2 released: http://community.aegirproject.org/3.0-beta2

Time for a release candidate...?

First release candidate of the 3.x branch is is out, see http://community.aegirproject.org/3.0-rc1

Still have to find time to fix debian packages ...

       ___
    .-     \
   /   _    \
  |  /   \   \
   \|     \   \
    \      \   \
     \      \   \
      \     _\   \
       \  /       \
        \|         |
         \  ~      |
          \.__ ~   \
              \     \
               \     \
                \     \
                 \ ._=_\
                  \/    >
                   ` \\\
                  .  \\\\   .
                 .    |||| .   .
                _________________
               <_________________>
                \ _________o___ /
                  \    o  .   /
                    \   .   /
                      \   /
                       | |
                       | |
                       | |
                       | |
                    ___| |___
                 _--         --_
                   -----------