This page is being moved to http://docs.aegirproject.org/en/latest/community/release-process/

This page aims to document our release process. It documents the release cycle, but also the steps required to make a release.

1. The release cycle

In general, each major Aegir release comprises a simultaneous release of all the modules that are part of the project. We generally go through several testing releases (alphas, betas & RCs) before doing the first stable release on a branch.

• First an alpha is released to test new functionalities and to accomplish the goals decided in the Project Roadmap for that major version. Example: 0.4-alpha1, 0.4-alpha15
• When we have covered most of the functionalities outlined in the roadmap, we push out beta releases until no more critical issues show up. This is generally considered a soft feature freeze. Example: 0.4-beta1
• Then we go into full feature freeze and release a first release candidate (RC). Then a stable release branch is created, and the development branch is kept opened for development for the next stable release. This is generally considered a soft API freeze. Release candidates are made as long as critical bugs are found. Example: 0.4-rc1, freeze announcement
• Once the development branch has no known critical bugs, the stable release is announced. From there on only critical fixes (security, critical performance and critical bugfixes) are committed to the stable branch, and stable releases are published (without alpha/beta/RC) directly on the stable branch. The stable branch is in full API freeze. New features are generally committed to the development branch.

See also the tag and branch naming convention.

2. Steps for a release

For the specifics of release naming conventions and the cycle, see the branch naming convention.

2.1. Make sure Jenkins is all green

Look into Jenkins to see if all tasks have been performed without errors since the last commit. If there is an error, fix it before the release.

2.2. Verify that drupal-org.make specifies up-to-date versions

In the hostmaster project we maintain our own drupal-org.make file. Check that e.g. the ctools version specified is not out-dated.

2.3. Generating the release notes

We build complete release notes for every release. Those are made up of a summary of the release, an outline of key changes, of known issues, install and upgrade instructions and a full list of bugfixes and new features.

Using Git Release Notes for Drush

drush rn 7.x-3.0-alpha1 7.x-3.0-alpha2

The developers then proceed to format/edit the list of fixes as well as list other significant information/changes for this release. These notes end up becoming the Release Notes for the release, which are also entered in the debian/changelog file by the script below.

2.4. Running the release.sh script

Each time we make a new release, we run a script called release.sh in provision.

This script should only be used by the core dev team when doing an official release. If you are not one of those people, you probably shouldn't be running this.

This script does all the 'hard' work in that it doesn't forget all the very many places to edit version numbers etc of relevant documentation and other scripts. This includes install.sh.txt and upgrade.sh.txt.

note from just after 7.x-3.0-beta1: It's probably a good idea to disable the Jenkins jobs named 'D_aegir-debian*'. This could prevent later troubles in the 'Publish the Debian packages' section.

Paraphrasing from the script itself:

Next, we need to add the tag in hostmaster, and push it to the d.o repos. So in short, this sums up as:

Notice how we just provide the Aegir release number (1.10) to the release script, not the Drupal branch (6.x), which is hardcoded in the script to remove potential confusion.

Special, for 2.x: While we wait for core support in drush (issue #1991764) we need to manually modify the makefiles in hostmaster, drupal-org.make and hostmaster.make to point to the tags we lay down manually in hostmaster, hosting and provision (and maybe eldir). So this ends up being:

2.4.1. Optional: new Eldir release

If we do a major release (say a point zero release), we may want to make a new release of the theme (Eldir). This can also be performed if there enough new changes on the theme to warrant a new release on its own.

To do a new release of Eldir:

1. tag and push the tag
2. update the version to fetch in hostmaster.make
3. create a release node for Eldir

2.5. Test the manual install in Jenkins

Before making a full release, test the release in Jenkins. To do so, start a build of the launch the S_aegir_6.x-1.x_install job (or S_aegir_6.x-2.x_install job for 2.x) with the following parameters:

• the right release as the AEGIR_VERSION parameter
• the DRUSH_VERSION to match what is required for this release. (Currently '4.5' for Aegir 1.x)

If the build fails, delete the remote tags (using git push origin :6.x-1.7, for example), fix the bugs and start again.

2.6. Build the Debian packages

Build the package and upload to http://debian.aegirproject.org/. Jenkins can build and upload a Debian package for you with the S_aegir-debian-official job.

If you need to move the tags again, you will need to clear the testing archive using the R clear repo job, with the testing argument.

You can also build and upload the package yourself as explained in these detailed instructions. We first upload the package to the testing distribution, and it gets migrated down into stable after tests.

Special, for 2.x: build the package manually, see detailed instructions. It should be something like:

./release.sh 2.0-rc5
git reset --hard 6.x-2.0-rc5
git-buildpackage -kanarcat@koumbit.org --git-builder=debuild
dput aegir build-area/aegir2-provision_2.0~rc5_amd64.changes

See the detailed instructions for the dput configuration.

2.7. Test the upgrade in Jenkins

Once both of those tasks have executed successfully, you can test the upgrade of the Debian packages by running the following Jenkins job:

http://ci.aegirproject.org/view/Upgrades/job/U%20aegir%206.x-1.x%20deb%2...

(Note that this test is currently non-functional)

2.8. Creating release nodes on Drupal.org

Once the tags are pushed and release notes published, we create a release node with an excerpt of (and a link to) the release notes so that tarballs are created and issue queue versions updated.

This needs to be done in the hostmaster and provision (and hosting and (maybe) eldir for 2.x) projects on Drupal.org.

Note: this could be automated with the right stuff on Drupal.org.

Special, for 2.x: make sure release nodes are created in order! The projects shipped with hostmaster (hosting, eldir, etc) need to be fully released before the hostmaster release node is created!

2.9. Build the release in Jenkins again

At this point, it's possible that the tarballs on Drupal.org were not created properly. We want to test the real procedure, so run a your build again, but choose 'package' as the AEGIR_FETCH_MODE. S_aegir_6.x-1.x_install job

Note: The link provided may reference the wrong test, since there doesn't appear to be an AEGIR_FETCH_MODE parameter.

2.10. Publish the Debian packages

Finally, when the Debian packages are tested you will need to pull them into the stable release channel:

http://ci.aegirproject.org/view/Release%20scripts/job/R%20repo%20pull/

2.x note: we pull to testing (and stable since the betas), manually:

reprepro copy testing unstable aegir2
reprepro copy testing unstable aegir2-hostmaster
reprepro copy testing unstable aegir2-provision
reprepro copy testing unstable aegir2-cluster-slave

3.x note: we pull to stable (since the betas), manually:

reprepro@zeus:~$ reprepro copy stable unstable aegir3
reprepro@zeus:~$ reprepro copy stable unstable aegir3-hostmaster
reprepro@zeus:~$ reprepro copy stable unstable aegir3-provision
reprepro@zeus:~$ reprepro copy stable unstable aegir3-cluster-slave

If Jenkins has managed to build .debs and upload them before you've have a chance to pull them into testing/stable, you can manually remove them like so:

reprepro remove unstable aegir2-cluster-slave aegir2 aegir2-provision aegir2-hostmaster

This should be prevented by disabling the Jenkins jobs named 'D_aegir-debian*' before starting to push the release tags.

You can then re-upload the new .debs you've generated, using the '-f' (force) flag:

dput -f aegir build-area/aegir2-provision_2.3_amd64.changes

After doing that, you can re-run the 'copy' commands to publish the .debs to the appropriate releases.

2.11. Publish the release notes widely

Once all this is done and the tarballs are generated, the release notes are published in:

• The handbook (this is where the release notes live!)
• A link to the release notes on the frontpage block
• An event in the calendar
• A discussion post (don't forget to make it 'sticky' & remove stickiness from the previous announcement)
• Update the version in the script upgrade page
• The topic of the IRC channel
• The aegir-announce mailing list (announce@lists.aegirproject.org.)
• Twitter as @aegirproject

Optionally, blog posts on koumbit.org, mig5.net, and elsewhere may go into further detail about significant changes, screencasts etc.

Debian is one of the main supported operating systems in Aegir. For other systems, see Operating System Support. See also the following instructions:

• Install using Debian packages
• Upgrade using Debian packages

The following is aimed at developers wishing to maintain their own Debian packages or work within the packaging framework.

1. Basic requirements

You need the following packages to build the Aegir Debian packages:

apt-get install devscripts git-buildpackage

See also the section below on Adding a new uploader.

2. Building a package for a new release

Assuming we have just released 2.0-alpha2, those instructions will merge that code into the upstream branch (which is used to create the Debian diff) and then merged again in the debian branch (where the Debian code lives). We then use git-buildpackage to build the package and tag it, then push those changes back in the repository.

Note: notice how the version number is slightly different in Debian - we use the "magic" ~ separator to indicate that 2.0~alpha2 is actually lower than 2.0...

The packages are initially uploaded to the "unstable" repository for initial test builds. The idea is that this final package can be moved to "testing" for broader testing, using the command:

When confirmed as ready, it is migrated to the stable repository, using the command:

3. Building a branch package

Sometimes you want to have a test package for a given branch without going through a full release. Here how it's done.

This is also available in the Debian package as:

4. Installing packages manually

We also make sure our custom makefile fetches the right one from provision:

5. Developing on Debian

To develop third party extensions to Aegir on Debian, it is recommended to install the Debian packages. If you are working on Aegir core, this could be a bit trickier since the files are not where you expect them to be and are not deployed as git repositories however.

You can, however, copy in place a .git directory using the following:

This will bring back a bunch of files that are removed from the Debian package, so it will yield warnings on uninstall of the Debian package but it should otherwise work.

You can do something similar with the frontend.

6. Package versioning

The stable repository should contain the latest release. The testing repository will also contain the latest release (unless we're in the process of building a release) but could have fixes to the Debian package that are being tested. The unstable repository is automatically built from the stable branch and may be broken.

To see what changes are done to the Debian package, see the debian/changelog which is maintained on the debian branch. To see which version of the package is currently available in the repository, you will unfortunately need to parse the Packages file for unstable, testing or stable.

7. Adding a new uploader

To enable a new maintainer to upload to the Debian repository at debian.aegirproject.org, something like the following steps will have to be followed:

Create a ~/.dput.cfg with the following entry:

Next, GPG keys will have to be authorized to upload to the repository:

8. Replacing an expired key

9. How the archive was built

The following documentation was used: https://wiki.koumbit.net/RepreproConfiguration

This is a brief outline of development plans for Aegir.

Update: this roadmap is not up to date anymore. Effectively, 0.4 and parts of 0.5 and 0.6 were all squashed into an API-stable 1.0 release published on Drupal.org in spring 2011. 1.0 is now in maintenance mode and only critical bugfixes will be accepted in the tree. This roadmap is therefore superseded by the 2.0 roadmap.

Note that all formal Aegir releases (ie. not those marked, "alpha", "beta" or "release candidates" or "RC") are production-ready. We strive hard to maintain good code quality and Q/A by frequent releases and alpha/beta/RC stages before those formal releases so even if the releases are marked 0.x, it's not because they are not stable or ready, it's simply because the API is not stable (see below).

0.1 - "Sites" - Single platform support

Solid release for Drupal 5 platform. Will not be able to upgrade. Production ready.

0.2 - "Upgrades" - Multiple platforms support

Support for more than one Drupal release. Support for migration between Drupal releases. Experimental support for remote SQL servers. Frontend still in Drupal 5.

0.3 - "d6" - Drupal 6 frontend support

In the backend: bugfix release of 0.2. In the frontend: port to Drupal 6.

0.4 - "Cloud" - Multiple servers support

Support ssh as communication channel between multiple servers (see this issue) Move sites between servers, and support for multiple db servers and moving between them.

Release goals for 0.4

0.5 - "apt-get" - proper deployment procedures

proper deployment procedures (features? proper project management? etc)

0.6 - "UX" - User interface improvements

Clean up and make the user interface friendlier.

1.0 - "API" - API freeze

A stable, published API for Hostmaster modules that will be frozen during the whole lifetime of the 1.0 branch to ease long term support for third party extensions.

From there on...

Extension modules

There is also a host (pun intended) of provisioning tasks that it would be nice to see created:

• LDAP (open LDAP)
• Solr Search (Tomcat)
• Jabber (ejabberd)
• DNS (Bind, DNSmasq etc - Actually already implemented in the 0.4 line)
• Pound (load balancer)
• Email (Zimbra)
• An RDF triple store (needs more research)
• Asterisk (voicemail, proxy)

Mass site operation modules

• Search (could be related to Solr)
• Statistics (info on nodes/comments/users etc. across all / many sites)
• Logging (centralized logging overview, might just be web interface for syslog)
• Spam / Comment moderation (we had some discussion about writing a Mollom module that works across sites)

Feel free to contact the developers if you are interested in pitching in to work on one or more aspects of Aegir.

Following the Drupalcon Chicago 2011 BOFs discussion, the community came up with a series of ideas and wishlist items for the upcoming 2.0 release. This roadmap may be updated or trimmed down as development goes ahead.

We do not commit to doing all of this for 2.0, this is mostly a wishlist of what people expressed were priorities for them during the brainstorm. If people want things to move forward, they will need to submit patches or create feature branches, basically lead development on the feature you want. This page can be used to coordinate overall leadership of those issues, while pointing to the Drupal.org issue queues for the specifics.

This roadmap supersedes the previous 1.0 roadmap.

Update: this roadmap is very ambitious, and should be considered more as a "wishlist". What we agreed on during the february 6th 2012 scrum was that we would focus on those items, in order of higher to lower priority:

1. Autoloaded classes (means we drop support for PHP 5.2 and below)
2. Drush 5 support

Once all those are done, 2.x should go in beta and once there are no criticals, it gets release, even if we don't have all the other features listed below.

Update: this is superseded by this roadmap: http://community.aegirproject.org/discuss/another-stab-short-and-long-te...

1. Drush collaboration

We want to collaborate more with the good people in the Drush project. We had good conversations at Drupalcon and hope to keep on having more about how to do staging, sharing code, working with contexts and aliases and so on.

This collaboration should permeate the whole 2.0 release cycle, as a lot of goals here overlap work already happening in the Drush project. We have a long tradition of leading development of new features in Drush, by first implementing them in Provision, and we should continue that trend, with a focus on merging those changes back up into Drush, and eventually removing them from Provision in 2.0.

Koumbit plans to keep on taking care of the Drush Debian packages and coordinate with the Drush team as much as possible.

1.1. Sending more code upstream

Our "contexts" code could be refactored and sent upstream. provision-save would be a likely first target, along with the persistent "contexts" classes. Note that we have hit a significant wall in the current API because it is hard to interoperate with existing server and site contexts from the outside of the class, so that's something that should be cleared up before going ahead with those merges.

1.2. Removing common code

At the very least, we should start removing common code between site-install and provision-install. The new drush archive command should also replace our builtin provision-backup, and provision-save may be refactored around drush_save_config() too (see issue #736686 for this).

1.3. Standard archive support

... which brings us to the standard archive format. Drush and Aegir developers have collaborated to create a common format to export and import Drupal sites. A single archive could bundle one or many sites, including site-wide code, so this is a significant difference (and improvement) over the current de-facto Aegir standard.

We want to support that new format. Full multi-site archives should be imported as platforms, while Aegir could keep on exporting single-site archives for standard platforms, like OpenAtrium or other distributions.

1.4. Unit testing

Drush has started to implement unit testing with PHPUnit in Drush 5 (see the tests directory for samples), and we should jump in that party, extending those classes and unit-testing the hell out of Aegir itself. That will make merging features into Drush easier and make sure we have no regressions while doing so.

2. Multi-server improvements

While Aegir 1.0 has multi-server support, it is far from ideal or complete, and we wish to harden that design in 2.0.

2.1. From a hub-spoke to a mesh model

The current model where there is one main server (the "hub") where all platforms and sites are created and then synced to remote servers (the "spokes") seems to be showing scalability issues and concerns about where the authoritative data should be.

For example, it's currently not recommended to allow developpers to access sites on remote servers, as the authoritative data resides on the hostmaster site. Another issue is that aliases are maintained only on the master server, and therefore are not accessible on remote servers. Finally, the fact that drush and provision are not installed on remote servers make some operations unnecessarily slow as we need to make the operation locally and then sync the result.

The alternative has yet to be discussed. We especially want to chime in with the Drush community here to see how the best practices should be. The conversation has started, and with the migration of Drupal.org to git, a lot of possibilities just opened up, with a lot of people being all of a sudden more familiar with this excellent too.

In general, it should be possible to expect remote servers to have drush and provision installed and be relatively independent from the "master" server. A design like this could eventually mean that Aegir could manage other Aegir sites and upgrade them. It is the "mesh" design, of which the "hub and spoke" model is only a subset.

This follows the practice of "tools not policy" we are heading towards: we leave the mesh vs hub/spoke decision to the site administrators and provide the tools to support both approaches the best we can.

Koumbit plans to spearhead this effort this summer.

2.2. Improve cluster support (done & backported to 1.7)

The current multi-server model doesn't support clusters and shared filesystems very well. Aegir 2.0 should allow scaling your web hosts horizontally by spreading a single site amongst multiple servers. While 1.0 can setup sites on remote servers, it follows more the concept of "sharding", spreading different sites amongst different servers than load balancing all sites amongst all servers.

This involves supporting load balancers (e.g. IPVs, Pound, Varnish), maybe through the existing "cluster" service, but also shared filesystems (e.g. NFS, OCFS, GFS, GlusterFS), maybe through a new "fileserver" service.

Koumbit plans to spearhead this effort this summer.

Update: this has been implemented with the "web_pack" module, which will be released with 1.7, deprecating the cluster module. 2.x will remove support for the current "cluster" module. See also the updated documentation.

2.3. Optimizing clones and migrates

We quickly mentionned git support above, but this could lead to significant improvements, for example by using git clone --shared instead of the traditional "backup and deploy" approach to clone/migrate sites.

There is certainly the possibility of rewriting clone to optimize away "backup and deploy" and merge them in a single operation that could use copy on write mechanisms like hardlinks (cp -al), git tricks (git clone --shared) or filesystem snapshots (e.g. BTRFS snapshot directory/file support).

Once deploy is optimized, we could consider hooking it the Drupal 7 or third party unit tests to rollback on such failures.

Those optimizations would need to integrate with and support the multi-server model elegantly too, especially the hypothetical fileserver service.

3. Modularization of more systems

Aegir 1.0 is already pretty modular: "services" are an abstract concept that can be implemented and inherited. For example, the "HTTP service" has four implementations: Apache, Apache-SSL, Nginx and Nginx-SSL. The database and DNS layers are also abstracted that way.

But more can be done here.

3.1. Modular backup system

Right now backups can be pretty heavy and use the venerable (1979!) tar backup format and utilities, which made Aegir portable to almost any UNIX operating system. It's a good start, but it's highly inefficient. As mentionned above for the clone and migrate optimization, we could also use modern filesystem features like snapshots or use git support. Another suggestion was to use S3 or similar services for offsite backups.

The basic idea here is that backups should be extendable - if you want to backup in your shoebox, Aegir should allow you to write a plugin for it. There was some initial work done by computerminds on github.

3.2. Modular platform support

This is also known as the alien platform support, that is - being able to install other "things" than Drupal in the backend, for example (oh the heresy!) Wordpress. This involves ripping apart the "platform" code in the frontend and the backend to make it more CMS-agnostic, so that Drupal is just one of the implementations.

This would make sense of course if at least another implementation would be supported. This could also involve merging the site and platform creation forms for those platforms that do not support multi-site like Drupal does (so that creating a site effectively create a platform).

3.3. Modular queuing system

The current queuing system is what we informally call the "ghetto queue". It's a cron job that pulls tasks from a MySQL database. While this scales well for a few sites, on busy servers it's a total nightmare, especially for mass migrations. Tasks stack up and concurrency is not managed at all. This needs to be completely redone.

A possibility is to use Drupal 7's abstracted queue API and let administrators implement their own queuing system according to their local APIs.

The new queuing system could be a key part in how the multi-server "mesh" model would be implemented. It could also be how non-Drush backends could be handled by Aegir - in that scenario, Aegir would become an interface for a standard queuing system, yet to be determined, although a lot of ideas are flying around: Jenkins/Hudson, AMPQ, Drush itself, etc. See this evaluation for that decision.

Koumbit plans to spearhead this effort this summer.

4. Other features

4.1. Automatic upgrades

There were a few discussions around managing platforms automatically. The implementation of hosting-import is one of the building blocks of this, but there remains some fine-tuning for this to work out of the box, especially for new users, some of which have requested that we can build makefiles straight from the frontend, a bit like how it's done on drushmake.me. One could also use feature servers feeds to update their platforms. Again, we should leave the policy to the user or at least make this pluggable.

This mostly consists of automating the creation of new platforms, the upgrade of sites between platforms and garbage collection of old platforms.

4.2. PostgreSQL backend support

The backend database layer (the "db class") now supports only MySQL, that is, while the Aegir frontend could technically run in PostgreSQL (although that is still unsure), the backend can't create sites in a PostgreSQL database.

Most of the work here will be around supporting user credentials handling, creation and destruction, which are fairly different between postgres and MySQL. The issue for this is #585796.

4.3. Statistics improvements

Work has already started at Koumbit to implement a "statistics" queue that would mostly pull Apache logfiles and parse it for size (and CPU timing) information. This is to implement bandwidth and CPU quotas, but could be extended in a more generic "statistics" queue that would collect all sorts of information:

• if your Drupals need to be upgraded or are secure (the basic "status report")
• how many modules/themes/profiles/libraries are installed (populating the frontend data)
• how many users/nodes/fields instances do you have?

All this could be collected in a nice dashboard that would outline client, site or platform-specific information.

4.4. Full DNS support

The DNS support in the backend is already pretty mature, but it's not really intuitive how it works and how to integrate it into existing infrastructures. Issue #922280 details all the next steps required here, but we can already say we hope to have a zonefile editor in the frontend, probably based on D7 entities, reasonable access control for zones, registrar support and "host my mail on gmail button" type of wizards.

This could potentially be picked up by a GSoC student.

4.5. Improved intersite security

We are already going through some hoops to make sure the database credentials are not accessible from one site to the other. The credentials are stored in the Apache environment and cleared out as soon as they are used, which makes finding them in settings.php impossible. Koumbit has also worked on a Provision ACL module that implements POSIX ACLs on files which allow more granular access controls on files.

But there are other security issues remaining that we should be looking into, especially the way Drush and Drupal are bootstrapped during tasks, which is currently insecure.

Koumbit plans to spearhead this effort this summer.

5. Contrib modules

Other contrib modules may have different roadmaps, but they must respect the release naming conventions. Contrib modules should aim for a 1.y release now, that will be compatible with the 1.x series. 2.x modules should be ported to Drupal 7 and follow the API (in development) of the 2.x series. Modules do not have to follow the minor version numbers of Aegir. For example, Provision ACL 1.1 is compatible with any release of the 1.x core series.

We are also considering making point releases of the backend and the frontend independent, so that Provision 1.1 and Hostmaster 1.2 could be release independently.

5.1. Other modules roadmaps

This is a short index of other modules roadmaps to 2.0:

• Ubercart integration (uc_hosting 2.0)

Plan for porting Aegir to D7 and creating a DNS editor. A project for Google Summer of Code 2011.

Please offer advice on how to improve the plan I've outlined below.

Relevant links: Hostmaster sandbox for GSOC2011

Before May 24:

• Review Git docs and other resources to learn more about using Git.
• Review issues/patches relevant to D7 port and DNS editor.
• Review api.aegirproject.org and community.aegirproject.org/developing.
• Discuss planned work with aegir maintainers.
• Refine plan below based on what I've learned from the handbook, api, and aegir maintainers.

Week one: Work on porting Aegir theme Eldir to Drupal 7. Finalize plans for porting the Aegir modules and install profile.

Week two: Finish porting Eldir to Drupal 7. Port the Aegir Hosting module to Drupal 7.

Weeks three through six: Port the Task, Client, DB Server, Package, Platform, Site, and Web Server modules to Drupal 7. Test ported modules.

Weeks six through nine: Port modules Alias, Clone, Cron, Migrate, Quota, Signup, Task, and Web Cluster to Drupal 7. Test ported modules.

Weeks ten and eleven: Work on the DNS zonefile editor.

Weeks twelve and thirteen: Continue testing ported projects and the DNS zonefile editor. Update documentation to reflect changes in the upgrade to Drupal 7.

Since we have now a bigger team of people interested in the project (contributors in the queue, outside the queue, people at Koumbit, the community site, my my!!), we (koumbit) feel it would be important to start doing weekly scrums again.

Nothing complicated: just a 15 minutes where we agree we try to be available on IRC to talk about various issues that have or will come up during the week. No work, just talk.. to quote wikipedia:

• The meeting starts precisely on time.
• All are welcome, but only “pigs” [devs] may speak
• The meeting is timeboxed to 15 minutes
• The meeting should happen at the same location and same time every day
• During the meeting, each team member answers three questions:
• What have you done since yesterday?
• What are you planning to do today?
• Do you have any problems preventing you from accomplishing your goal?

(It is the role of the ScrumMaster to facilitate resolution of these impediments. Typically this should occur outside the context of the Daily Scrum so that it may stay under 15 minutes.)

These occur via IRC on the #aegir channel twice a week at separate times:

Every Monday at 20h00 UTC. This works out to be:

• 11h00 in Los Angeles, USA (PDT)
• 15h00 in Montreal, Canada; New York, USA (EDT)
• 19h00 in London, UK (GMT)
• 06h00 in Melbourne, Australia (EST)(on Tuesday)

(See this useful tool for how we settled on those times.)

Every Thursday at 10h00 UTC. This works out to be:

• 03h00 in Los Angelas, USA (PDT)
• 06h00 in Montreal, Canada; New York, USA (EDT)
• 11h00 in London, UK
• 12h00 (noon) in Warsaw, Poland
• 20h00 in Melbourne, Australia (EST)

We will keep logs of these here for future reference.

Archive of the weekly scrum from 2010

(03:00:54 PM) anarcat: hi.
(03:01:08 PM) anarcat: so now is the time for our newly established weekly scrums :)
(03:01:24 PM) anarcat: of course, mig5 is not there and vertice either, but i'll still do my part,
 just to kickstart this
(03:01:32 PM) hadsie: hey anarcat
(03:01:54 PM) anarcat: hey hadsie
(03:03:30 PM) anarcat: so basically, i haven't done much wrt to aegir this week, i'm busy
 with other koumbit work
(03:03:39 PM) anarcat: you're going to hear this often from me, unfortunately :)
(03:04:03 PM) anarcat: my latest thing though is the creation of a debian package for provision
 that can install and upgrade aegir automagically, it's pretty neat and needs testing
(03:05:42 PM) anarcat: i have contacted other debian developpers to get their feedback about
 the possibility of uploading that package straight into debian
(03:07:24 PM) anarcat: the followup for the debian package happens here: 
http://drupal.org/node/490004 and here: http://bugs.debian.org/532923
(03:07:36 PM) sfyn: hey folks
(03:07:36 PM) anarcat: in other news i started looking at STS here: 
http://drupal.org/node/986312
(03:08:04 PM) anarcat: so that's it for my past work, in the next week i'll try to:
(03:08:22 PM) anarcat: figure out proper permissions for multi-(shell)user setups in aegir
(03:08:49 PM) anarcat: right now a lot of our devs use sudo -u aegir to do stuff and that's quite 
messy, we're going to try to figure out the minimum set of perms for that to work, maybe with 
ACLs
(03:09:03 PM) anarcat: we also need to figure out how we maintain site-specific packages in 
remote servers
(03:09:26 PM) anarcat: and i want to start fixing DNS in the frontend, but we are slowly pushing
 back our objective of having DNS in production to after christmast
(03:09:30 PM) anarcat: so that's it for me
(03:09:42 PM) anarcat: hi sfyn :)
(03:09:43 PM) anarcat: sfyn / ergonlogic / mvc : anything to add?
(03:11:24 PM) simesy: hey i actually made the scrum, (but only because I had to get up for a
 job and now I have to go :P)
(03:11:35 PM) anarcat: :)
(03:11:35 PM) anarcat: i see
(03:11:39 PM) anarcat: well, congratulations :)
(03:11:42 PM) sfyn: I have been sick all week and trying to catch up on my rpod stuff
(03:11:51 PM) sfyn: So very little progress to report
(03:11:59 PM) sfyn: I have a guy who is interested in writing tests for us
(03:12:13 PM) sfyn: Luigi - are you here?
(03:12:38 PM) sfyn: A guy in montreal, but he is a little new to the fabulous world of drupal,
 and FLOSS in general, I get the impression
(03:12:46 PM) sfyn: But he has done unit testing work before
(03:13:00 PM) sfyn: Maybe we should get him to come into the office so we can orient him
(03:13:18 PM) sfyn: hadsie: hey man
(03:14:07 PM) anarcat: thank you sfyn
(03:14:16 PM) anarcat: so our little scrum is almost over, anybody got anything to add before
 we move on?
(03:16:26 PM) anarcat: thank you for your attention, and see you next week!

(02:57:33 PM) ergonlogic: everyone: Weekly scrum being in ~5 mins
(02:57:57 PM) mig5: trying to wake up :)
(03:01:49 PM) anarcat: hey hey!
(03:01:55 PM) anarcat: good morning world!
(03:02:01 PM) omega8cc: hey
(03:02:10 PM) ***anarcat tries to play the gooooood moooorning vietnam cue here
(03:02:12 PM) mig5: good morning, here at least :)
(03:02:16 PM) anarcat: so
(03:02:31 PM) anarcat: welcome to our weekly scrum session, we have ... 13 minutes left
(03:02:35 PM) mig5: woot
(03:02:41 PM) anarcat: we failed at the first directive, and i'm sorry for that (start on time, damnit!)
(03:02:50 PM) ergonlogic: my fault
(03:02:51 PM) anarcat: and i'll start with my stuff, i didn't do much last week
(03:03:02 PM) anarcat: in fact, nothing i can remember
(03:03:14 PM) anarcat: next week is likely to be similar as i'm over[load]ed with thousands of internal needles
(03:03:20 PM) anarcat: that's all for me :)
(03:03:22 PM) mig5: yay
(03:03:29 PM) mig5: ok
(03:03:47 PM) mig5: to carry on that tune, i didn't do much last week, i have been trying to catch up on some tickets
(03:03:53 PM) mig5: my immediate aims are,
(03:04:04 PM) mig5: to test the debian packages now that i know they're in unstable
(03:04:07 PM) mig5: which i will do today
(03:04:24 PM) mig5: and possibly help ergonlogic with this clients permission stuff
(03:04:45 PM) mig5: after that i will start looking at the 'for review' patches in the queue per our beta2 plans
(03:04:51 PM) mig5: but that may not get to happen until next week
(03:05:01 PM) anarcat: rc2 you mean
(03:05:02 PM) mig5: that's about it from me
(03:05:06 PM) anarcat: ok
(03:05:08 PM) mig5: oh really
(03:05:10 PM) mig5: rc2?
(03:05:12 PM) anarcat: er
(03:05:13 PM) anarcat: no
(03:05:15 PM) anarcat: i don't
(03:05:16 PM) mig5: haha
(03:05:18 PM) ***anarcat is on crack, nevermind
(03:05:24 PM) anarcat: i was confusing us with drush, sorry
(03:05:29 PM) mig5: i would be happy to push for rc1 :)
(03:05:32 PM) anarcat: ergonlogic?
(03:05:48 PM) anarcat: sfyn is offline today, but i know he tried to get back into things and will keep on doing that
(03:05:50 PM) ergonlogic: well, I'm working on the permission issue that mig5 mentioned
(03:06:02 PM) ergonlogic: and the udev dependency
(03:06:11 PM) anarcat: right, about that
(03:06:22 PM) anarcat: i'm sure that moshe_work and other drush people would love to see that land in drush 4
(03:06:27 PM) ergonlogic: just trying to get into the swing of things, and familiarize myslef with some of aegir's inner workings
(03:06:32 PM) anarcat: but i'm not sure we'd make it for rc3 at this rate
(03:06:51 PM) anarcat: how do you feel about this?
(03:07:32 PM) ergonlogic: well, I think I'm about half way there on that issue
(03:07:40 PM) anarcat: alright
(03:07:41 PM) ergonlogic: but I still nee to post a patch
(03:07:47 PM) ergonlogic: s/nee/need
(03:07:48 PM) anarcat: ok
(03:08:11 PM) anarcat: *and* it would then need to be ported up to drush... so we can safely assume we won't make it into drush 4, those guys are in a rush :)
(03:08:20 PM) anarcat: speaking of drush
(03:08:28 PM) mig5: in a rush or in a drush? :)
(03:08:33 PM) anarcat: drush is that somebody omega8cc tested aegir with drush 4-rc1, and it works
(03:08:34 PM) anarcat: hehe
(03:08:35 PM) ergonlogic: groan
(03:08:40 PM) mig5: sorry..
(03:08:44 PM) anarcat: hehe
(03:08:49 PM) anarcat: alright
(03:08:55 PM) mig5: yes Vertice asked me to test that too, another thing on my todo list
(03:08:59 PM) anarcat: so
(03:09:00 PM) mig5: glad someone else did
(03:09:02 PM) anarcat: i guess one last thing
(03:09:32 PM) anarcat: we heard from vertice finally and he's coming back after a small hiatus, he's going to concentrate on documentation stuff and helping us figuring [stuff] out
(03:09:40 PM) anarcat: he's also eager (hehe) to release an rc
(03:09:45 PM) anarcat: so maybe it's something we should consider
(03:09:49 PM) ***anarcat looking at rc bugs
(03:10:22 PM) mig5: we have had the benefit of not having too many new criticals. i think if we can tie off some existing patches, we could look at that perhaps
(03:10:26 PM) anarcat: so most of those are postponed (so needs testing and closed: worksforme)
(03:10:44 PM) mig5: do you have a link to the rc bugs
(03:10:50 PM) anarcat: http://drupal.org/project/issues?text=&projects=provision,+hosting,+hostslave,+eldir,+Hostmaster+(Aegir)&status=Open&priorities=1&categories=All
(03:11:05 PM) anarcat: one is the freaky multiserver thing, i'd like adrian or somebody else to look at that one as i don't have the resources or time or brain to look into this
(03:11:11 PM) anarcat: that one is http://drupal.org/node/976300
(03:11:20 PM) anarcat: the other one is the site form optimisation: http://drupal.org/node/955854
(03:11:27 PM) anarcat: which could be postponed to post 0.4
(03:11:33 PM) anarcat: so we need testing, basically
(03:11:39 PM) mig5: yeah i'm still not convinced the multiserver thing is just someone trying to do something we don't support at all (i.e spoke vs mesh model)
(03:11:42 PM) mig5: yep
(03:11:49 PM) anarcat: alright
(03:12:03 PM) anarcat: so i would favor more a testing + rc1 than a beta2 at this point
(03:12:07 PM) ergonlogic: I'm into testing the multi-server stuff, if that's on the menu
(03:12:17 PM) anarcat: ergonlogic: it is, take a look at http://drupal.org/node/976300
(03:12:20 PM) ergonlogic: and dns
(03:12:29 PM) anarcat: dns + ssl integration needs testing too: http://drupal.org/node/934908
(03:12:44 PM) anarcat: and this should probably just be closed: http://drupal.org/node/950118 (new servers probably work fine)
(03:12:52 PM) anarcat: that one is more hairy: http://drupal.org/node/884090
(03:12:57 PM) anarcat: not suer about it
(03:13:12 PM) anarcat: but really, i believe we could just test those quickly and release next week, how about that?
(03:13:56 PM) mig5: sounds good, perhaps late next week, allowing me my thursday/friday where i can spend like a whole day looking at some of this
(03:13:56 PM) ergonlogic: I'll look into provisioning some new servers :)
(03:14:02 PM) anarcat: ok
(03:14:04 PM) anarcat: awesome
(03:14:07 PM) anarcat: okay, anybody else has something to add here?
(03:14:24 PM) anarcat: so thank you for attending, and have a nice day!
(03:14:31 PM) ergonlogic: cheers!
(03:14:34 PM) mig5: cheers

07:00 <@mig5> scrum time
07:00 <@anarcat> hi
07:00 <@mig5> morning
07:01 <@anarcat> good morning!
07:01 <@anarcat> not much to report on my side again, other than i forgot to book a session for drupalcon :/
07:01 <@mig5> hehe
07:01 <@anarcat> we're working on LDAP support and we'll focus on intersite security after christmas
07:01 <@mig5> i did make a tweet after i saw there are three aegir related proposals
07:01 <@mig5> oh sweet! LDAP++
07:01 <@anarcat> add a way for aegir to run tasks as a real user instead of itself, so that site A can't see site B's stuff
07:03 <@mig5> cool - that's it from you?
07:04 <@anarcat> yes, sorry
07:04 <@mig5> no worries
07:04 <@mig5> ok, so (again) i haven't done much
07:05 <@mig5> i tried to address some of the for review tickets in the queue, committing two of hadsie's work which i tested
07:05 <@anarcat> that's much :)
07:05 <@mig5> i didn't get to test your debian packages against another squeeze install but i did comment on the ticket about what i think the issue is there
07:05 <@anarcat> yeah, you're right about the issues, feel free to fix if you have time
07:06 <@mig5> but mainly i have been just staring at the queue and feeling out of steam (again), I wonder whether it is time to look at adding more people to the project
07:06 <@anarcat> i agree
07:06 <@mig5> as i feel i'm getting less and less useful, and vertice is taking a break etc,
07:06 <@mig5> and you are tied up a lot with internal stuff (which is fine)
07:06 <@anarcat> i don't feel you're less and less useful though :P
07:07 <@mig5> well that's ok :) i think it speaks for itself
07:07 <@mig5> and things have slowed down so lets get some more hands on deck basically.
07:07 <@mig5> also, i have a client at the moment who is interested in seeing two things happen:
07:07 <@mig5> a dns frontend and scheduled tasks
07:07 <@mig5> Steven Jones has been doing great work with scheduled tasks and created a contrib project hosting_backup_queue
07:08 <@mig5> i was going to ask whether Koumbit were already working on a dns frontend
07:08 <@mig5> we can discuss that later if you like
07:08 <@mig5> and that's about it from me
07:09 <@anarcat> ok, anybody else?
07:09 <@mig5> maybe it would be nice to summarise these scrum sessions as a 'weekly aegir news' email to the mailing list, making people aware of stuff like Steven Jones' contrib project etc
07:09 <@anarcat> mig5: i have ideas on the frontend: 1) there should be code we can resurrect from older git repos and 2) i have a workflow for the blacklisting algorithm (can't let anyone host any zone can't we...)
07:09 <@anarcat> yep
07:10 <@mig5> i am happy to do so
07:11 <@mig5> (re: news)
07:11 <@mig5> ok -we are 11 minutes in anyone else have anything to add?
07:12 < erutan> re: news to save time you could always just dump the relevant irc log onto the open atrium site
07:12 <@mig5> we do that already, yep
07:12 <@mig5> maybe that's enough.
07:12 <@anarcat> yeah...
07:13 <@anarcat> alright, thanks for coming everyone!
07:13 <@mig5> cheers
07:13 <@mig5> cheers
07:14 <@mig5> adding the irc log now
07:15 < noecc> mig5: anarcat: vertice: and others  You have done great things with aegir.  Don't let your steamlessness get you down.
07:15 <@anarcat> :)
07:15 <@anarcat> thanks :)

Note that none of the core devs were in attendance for this session. Regardless, this is the discussion that ensued:

(03:01:56 PM) darthsteven: Is the scrum at 2005?
(03:05:10 PM) ergonlogic: I guess I could start, pending the arrival of the core devs
(03:05:28 PM) ergonlogic: This week I upgraded to beta2 and began testing remote servers
(03:05:58 PM) ergonlogic: the beta2 upgrade required debugging some misconfiguration I had done previously, but otherwise everything seems to be working fine
(03:06:32 PM) ergonlogic: so far, I can verify a remote platform, but can't yet provision a site on it
(03:06:48 PM) ergonlogic: so that'll be something I look at over the holidays
(03:07:03 PM) ergonlogic: finally, I published and api site
(03:07:27 PM) ergonlogic: currently at api.ergonlogic.net, but hopefully api.aegirproject.org will point ot it soon
(03:07:34 PM) ergonlogic: that's it for me
(03:07:49 PM) ergonlogic: happy holidays everyone
(03:08:07 PM) eft_: I started a Why Aegir wiki http://community.aegirproject.org/node/217
(03:08:35 PM) eft_: hope to add some graphics at some point
(03:08:50 PM) eft_: we need to market Aegir more :)
(03:09:50 PM) ergonlogic: eft_: agreed about the mktg, but the move to beta seems to have helped already
(03:10:35 PM) eft_: how so?  do you mean the perception of getting out of alpha?
(03:11:21 PM) omega8cc: I submitted my first attempt to resolve the issue with remote files being removed on site verify, testing it is welcome: http://drupal.org/node/976300#comment-3855932
(03:13:15 PM) omega8cc: the issue is mentioned on http://community.aegirproject.org/0.4-beta2
(03:14:00 PM) ergonlogic: eft_: yes
(03:14:31 PM) omega8cc: oh, and  www.drupal7releaseparty.org is hosted on Aegir
(03:14:52 PM) eft_: cool

Archive of the weekly scrums from 2011

07:01 <@mig5> Scrum time
07:01 <@mig5> who is here for the meeting, anarcat?
07:01 <@mig5> nope :)
07:01 <@mig5> sfyn: 
07:02 <@mig5> well i'll start. another week gone by without looking at DNS, but we have a good roadmap now thanks to anarcat, i may start looking at that today
07:03 <@mig5> we're now compatible with drush 4 (at the moment)
07:03 <@mig5> i cleaned up some of the hostmaster profile thanks to drush 4's supporting of drupal_set_message being sent to stdout during install profile execution, which identified some legacy stuff that could be removed
07:04 <@mig5> i'm going to look at dns, upgrades, and some multiserver stuff today hopefully
07:05 <@mig5> i also hope to look at darthsteven's new contrib module hosting_backup_gc http://drupal.org/project/hosting_backup_gc
07:05 <@mig5> and am trying to think of a nice way to let people list their contrib modules on teh community site. i wonder if we should have an inbuilt Featureserver for that sortof thing to let people upload them
07:05 <@mig5> thats it from me (i am talking to myself anyway? :) )
07:06 <@mig5> i'll leave it for another 5 min and if nothing happens, will drop that into the logs

06:59 <@anarcat> SCRUM START NOW!
06:59 <@anarcat> welcome everyone :)
06:59 <@anarcat> i'll start with myself
06:59 <@anarcat> i am just out of a lenghty (2.5 week) vacation
06:59 <@anarcat> which was very good
06:59 <@anarcat> i have done absolutely no aegir work since decembre
07:00 <@anarcat> and i don't plan on doing anything until monday
07:00 <@anarcat> at which point we'll update our prod server to head and try to make it work
07:00 <@anarcat> i had big unexpected issues last time with that http://drupal.org/node/1003700
07:00 <@anarcat> in general, i feel there's something very fishy with aliases, i feel this affects more than one of my server instances\
07:00 <@anarcat> i suspect it may be related to drush 3.3 or the drush package of
07:01 <@anarcat> so i'll be working on that
07:01 <@anarcat> i have also a huge backlog of internal aegir issues that may yield a few bugfixes
07:01 <@anarcat> this will be a good Q/A to maybe lead to an RC somewhere next week
07:01 <@anarcat> so that's it for me
07:01 <@mig5> nice one
07:02 <@mig5> i've not done much except, updated our makefiles to depend on drush 4 and new drush make
07:02 <@mig5> i also updated the upgrade script to remove some hardcoded crap and be more consistent with the install.sh
07:02 <@anarcat> coool
07:02 <@mig5> i *wanted* to work on DNS but sorry, I am just really struggling to do anything aegir :(
07:02 <@anarcat> you've actually done some real work, crazy ;)
07:02 <@mig5> well not really.. :s
07:03 <@mig5> finally, i'll just note on what i think is our most critical bug right now, and i hope to focus on this instead
07:03 <@mig5> http://drupal.org/node/976300
07:03 <@anarcat> Vertice: anything to add? how is the DNS change coming up?
07:03  * anarcat takes a look
07:03 <@mig5> verify a remote platform/site and it deletes shit in your site's /files dir :s
07:03 <@anarcat> right, ok
07:03 <@anarcat> mig5: i think it's good to sync only some files and not the whole dir
07:03 <@mig5> because we do these crazy syncs of the entire codebase *after just syncing the settings.php, and then the drushrc.php, etc*
07:03 <@mig5> yes
07:04 <@mig5> anyway, can discuss that later, just wanted to mention what i think i'll focus on for the moment
07:04 <@anarcat> that's very good.
07:04 <@mig5> and that's it from me
07:04 <@anarcat> and it it's RC indeed
07:04 <@anarcat> i need Vertice to do changes to the DNS to activate ergonlogic's API site so we have api.aegirproject.org
07:04 <@anarcat> anyone else wants to add something?
07:04 <@mig5> i'd like to add to that and possibly take over the hosting of aegirproject.org at least, so we can get that updated
07:05 < ergonlogic> thanks anarcat
07:05 <@mig5> or possibly even take over the DNS for aegirproject.org itself, in the event i ever need to move the mailing list server or something
07:05 < eft_> mig5 : +1 to that idea
07:05 <@mig5> just for the sake of speed, but it's up to devseed
07:05 <@anarcat> yeah
07:05 <@anarcat> i don't mind you hosting that, koumbit can also host DNS and the site
07:05 <@mig5> yeah either way :)
07:05 <@anarcat> i offered this to Vertice, i expect us to have DNS soon
07:05 <@mig5> cool
07:05 <@anarcat> (us = koumbit)
07:05 <@mig5> yep
07:06 <@anarcat> but for the site, yeah, it would be important to at least have a backup ...
07:06 <@mig5> darthsteven: feel free to chime in - you've been doing great work with contrib aegir stuff
07:06 < darthsteven> ah okay
07:06 < eft_> either way, it would be nice to increase the cookie timeout on community.aegir.org
07:06 <@anarcat> yeah, if anyone else wants to jump in, feel free to talk :)
07:06 < darthsteven> So I've been thinking mostly
07:06 <@anarcat> if you're doing dev on aegir, now's the time to talk (after darthsteven :)
07:06 < darthsteven> Mainly about provision contexts
07:07 < darthsteven> and provision-save and services and how all the pieces fit together
07:07 < darthsteven> I have an outline for a handbook page(s) that should document most of what's going on
07:08 <@mig5> oh that'd be nice. since you have chosen the bit that no-one understands how it really is meant to work :)
07:08 < darthsteven> Nothing new in contrib land from me this week
07:08 <@anarcat> cool
07:08 <@anarcat> i think Vertice did some work in that direction in the handbook already
07:08 <@anarcat> ok
07:08 <@anarcat> anyone else?
07:08 < darthsteven> mig5: yeah, it is complex...
07:08 < darthsteven> that's it from me
07:08 <@mig5> yes darthsteven http://community.aegirproject.org/node/41 have a read of that if you've not already
07:09 <@anarcat> cool
07:09 <@anarcat> ok last call, anyone else?
07:09 <@anarcat> anybody have time to log this into the community site?
07:09 <@mig5> sure
07:09 <@mig5> thanks all! goodscrum
07:10 <@anarcat> thanks!
07:10 <@anarcat> happy new year everybody, and thanks for attending!
07:10 <@anarcat> SCRUM END!
07:10 < darthsteven> 

(03:00:17 PM) anarcat: welcome to our weeeeekly scrum!
(03:00:28 PM) anarcat: good morning, good evening, wherever you are!
(03:00:39 PM) anarcat: those new to the scrum can read on them here; http://community.aegirproject.org/scrums
(03:00:43 PM) anarcat: otherwise i'll start
(03:00:57 PM) anarcat: yesterday i upgraded our prod server from alpha14 to beta2, and it went well
(03:01:00 PM) anarcat: mostly without an hitch
(03:01:05 PM) anarcat: i was really surprised, actually
(03:01:15 PM) anarcat: i expected to see the weird issues with aliases
(03:01:27 PM) anarcat: http://drupal.org/node/1003700
(03:01:30 PM) anarcat: but i didn't
(03:01:34 PM) mig5: pretty smooth upgrades from the later alphas
(03:01:44 PM) anarcat: however, when upgrading a client from alpha6, i had issues with the upgrade path
(03:01:56 PM) anarcat: http://drupal.org/node/973826
(03:02:08 PM) anarcat: the above contains a nice demonstration on how to fix the issues
(03:02:22 PM) anarcat: i am not sure we should fix anything there, as it's really hairy to fix and affects very few people
(03:02:25 PM) anarcat: not worth it, i think
(03:02:32 PM) anarcat: i have filed a bunch of bug nevertheless
(03:02:36 PM) anarcat: after our prod upgrade
(03:02:40 PM) anarcat: had performance issues with the migrate page
(03:02:51 PM) anarcat: which we fixed: http://drupal.org/node/1033072
(03:02:59 PM) anarcat: that needs testing, but maybe I can just merge it now
(03:03:13 PM) anarcat: we also have numerous issues with the site form that remain
(03:03:15 PM) anarcat: esp http://drupal.org/node/1033078
(03:03:23 PM) anarcat: ie. the ssl cert selection doesn't pop up
(03:03:37 PM) anarcat: and that page is still slow as hell
(03:03:41 PM) anarcat: which may be related to http://drupal.org/node/955854
(03:03:59 PM) anarcat: so that's it for last week
(03:04:06 PM) mig5: wow! :)
(03:04:09 PM) anarcat: next week i'll try to fix a shitload of bugs i have in the backlog
(03:04:15 PM) anarcat: that other koumbit workers reported
(03:04:24 PM) anarcat: mostly upgrade issues, sometimes contrib-modules (e.g. date) related
(03:04:27 PM) ergonlogic: anarcat++
(03:04:38 PM) anarcat: once i'm through this, i am thinking of looking again at a RC release
(03:04:45 PM) mig5: anarcat has taken over skynet again
(03:04:49 PM) anarcat: but i am curious what others think about this
(03:04:58 PM) anarcat: mig5: i wish...
(03:05:07 PM) anarcat: i still struggle to free some time for aegir here
(03:05:12 PM) anarcat: but that may get better with time
(03:05:17 PM) anarcat: my focus right now is stabilising our thing
(03:05:24 PM) mode (+v grugnog_laptop) by ChanServ
(03:05:30 PM) mig5: i am the opposite, i have the time but not the skills :)
(03:05:33 PM) anarcat: targeting feb. for stabilisation, then working on security during feb.
(03:05:39 PM) mig5: yes for RC, that's a good idea
(03:05:49 PM) mig5: i even forgot we agreed to jump from 0.4 to 1.0
(03:05:52 PM) mig5: in september
(03:06:01 PM) anarcat: re. taht, we still have 2 RC bugs
(03:06:04 PM) anarcat: http://drupal.org/node/1003908
(03:06:07 PM) anarcat: http://drupal.org/node/993944
(03:06:10 PM) anarcat: The bulk operations form for site listings shouldn't list install and import tasks
(03:06:14 PM) anarcat: ssl rollback failure
(03:06:25 PM) anarcat: we should consider the option of rolling back the bulk ops shit if it breaks stuff
(03:06:32 PM) anarcat: but that seems like an easy thing to fix
(03:06:36 PM) anarcat: the ssl rollback sounds more hairy
(03:06:46 PM) anarcat: but i think we can ship an RC with it as a known issue
(03:06:51 PM) mig5: yeah.. i opened a ticket here and there about bulk ops. not really major bugs, just little niggly things
(03:06:53 PM) anarcat: that's it for me
(03:06:55 PM) mig5: yeah
(03:07:01 PM) mig5: ok
(03:07:09 PM) anarcat: go mig5 !
(03:07:13 PM) mig5: in classic mig5 style i have done nothing
(03:07:15 PM) mig5: EXCEPT
(03:07:18 PM) mig5: http://drupal.org/node/976300
(03:07:26 PM) mig5: i fixed our major and possibly only data-loss bug
(03:07:39 PM) mig5: that was deleting stuff from a site's 'files'dir on a remote server on every verify
(03:07:43 PM) mig5: and hence migrate, etc.
(03:07:52 PM) anarcat: "just that"
(03:07:56 PM) anarcat: dude that's awesome
(03:08:00 PM) mig5: that was a major aegirwtf but it seems to be ok now
(03:08:07 PM) omega8cc: that fix makes rc possible, imo
(03:08:08 PM) anarcat: cool
(03:08:32 PM) anarcat: right
(03:08:36 PM) anarcat: mig5: what's up next week?
(03:08:43 PM) mig5: i don't think i've done anything else :s i have given up on the idea of getting anywhere with the dns stuff, so i won't make promises there
(03:08:44 PM) anarcat: dns? ;)
(03:08:47 PM) mig5: haha
(03:08:47 PM) anarcat: Vertice: you there?
(03:08:51 PM) mig5: damn
(03:08:52 PM) anarcat: hehe
(03:08:55 PM) anarcat: it's okay
(03:09:05 PM) anarcat: our discussion helped me rehash the roadmap, so it's all good
(03:09:39 PM) anarcat: mig5: anything else?
(03:09:53 PM) mig5: this is weird: http://drupal.org/node/1025972 and i think i've reproduced it, so i will probably take a look at that
(03:10:06 PM) mig5: it's not *too* critical but it means remote servers need a manual apache restart or something, after the task completes
(03:10:14 PM) anarcat: right
(03:10:15 PM) anarcat: ok
(03:10:15 PM) mig5: so this is just stability stuff
(03:10:22 PM) mig5: that's it from me
(03:10:28 PM) anarcat: i have seen weird ordering issues like this even in local, but i never found it to be a bug so far
(03:10:31 PM) anarcat: okay
(03:10:34 PM) anarcat: omega8cc / ergonlogic / others: any comments? what you did last week / will do next week?
(03:10:37 PM) anarcat: Vertice: ?
(03:11:10 PM) darthsteven: I didn't get chance to write up 'contexts' this week
(03:11:19 PM) darthsteven: But hope to next week
(03:11:23 PM) anarcat: awesome
(03:11:27 PM) anarcat: otherwise i want to say that we (the aegir project) are always looking for new blood
(03:11:34 PM) darthsteven: That's it from me
(03:11:49 PM) mig5: nice darthsteven, i am looking forward to learning how this stuff works :)
(03:11:55 PM) omega8cc: from me - I made a few important changes to nginx configuration and plan to submit all of them shortly, also next week I plan to submit nginx installer, promised long time ago
(03:11:59 PM) ergonlogic: nothing really on my end, though I've noticed some odd behaviour since updating to beta2, so I'll be looking through open issues and filing some bugs possibly this week
(03:12:12 PM) anarcat: we need testers (dl new release and report bugs, test existing issues), documentors (community.aegirproject.org/handbook!) and developpers (submit and review patches and we will love you and give you commit access)
(03:12:35 PM) anarcat: ergonlogic: awesome!
(03:12:44 PM) anarcat: omega8cc: patches to hostmaster-install? or bash scripting?
(03:13:28 PM) anarcat: otherwise, anybody else has somethign to say?
(03:13:35 PM) ergonlogic: oh, also DNS for api.aegirproject.org should shortly be working (thanks Anarcat!), so check out that resource
(03:13:42 PM) omega8cc: anarcat: mostly nginx conf templates, installer script (very simple bash) and some UI improvements
(03:13:58 PM) ergonlogic: It exposes some pretty spotty documentation in the code
(03:14:15 PM) anarcat: oh right, we are in the processing of transfering the dns to a new registrar (yay gandi.net!) and hopefully that will go without an hitch
(03:14:23 PM) anarcat: omega8cc: i'd love to see this factored into hostmaster-install
(03:14:33 PM) anarcat: ergonlogic: those could be reported as bugs, maybe...
(03:14:43 PM) mig5: sure
(03:14:45 PM) anarcat: ergonlogic: Vertice expressed interest in working on those documentation issues
(03:14:55 PM) anarcat: okay, so that's pretty much it, thanks for attending our daily scrum!
(03:15:03 PM) mig5: cheers
(03:15:05 PM) anarcat: have a nice day, wherever you are!
(03:15:09 PM) ergonlogic: that's what I had in mind, with maybe some doc patches where I can grok the code
(03:15:16 PM) anarcat: can somebody file this in the OA site?
(03:15:19 PM) darthsteven: Bad docs are bugs for sure
(03:15:21 PM) omega8cc: anarcat: that is simple installer and how-to for standalone nginx based installs,
(03:15:23 PM) ergonlogic: I got it
(03:15:29 PM) anarcat: ergonlogic: thanks
(03:15:37 PM) anarcat: scrum over, see you again next week :)
(03:15:38 PM) anarcat: ciao !
(03:15:40 PM) darthsteven: Thanks everyone
(03:15:43 PM) ergonlogic: Take care
(03:15:47 PM) omega8cc: ciao

07:01 <@anarcat> morning!
07:01 <@anarcat> scrum is late omg! ;)
07:01 <@mig5> hai!
07:01 <@mig5> oops
07:01 <@anarcat> sorry i'm late :)
07:01 <@mig5> too many emails to read
07:01 <@anarcat> first rule of scrums : start on time damnit! ;)
07:01 < eft_> people still use email?
07:02 <@mig5> only 1 minute off. i blame timezones
07:02 <@anarcat> so anyways
07:02 <@anarcat> i almost caught up on all my issues
07:03 <@anarcat> i reported a few following significant upgrades
07:03 <@anarcat> maybe that was last week
07:03 <@mig5> I think so :)
07:03 <@anarcat> i want to make rc tonight
07:03 <@mig5> !
07:03 <@anarcat> oh, we have deployed our first d7 platform here
07:03 <@mig5> nicely done.hefring in here runs on d7
07:04 <@anarcat> still waiting on actual tests for this - i think i'll just merge it in: http://drupal.org/node/1033072
07:04 <@anarcat> i agree with http://drupal.org/node/1039168 that path shouldn't be editable
07:04 <@anarcat> and well, that's it!
07:04 <@mig5> nice!
07:04 <@anarcat> i think that koumbit will rework its own roadmap next week, so i'll keep you up to date on that
07:04 <@anarcat> so how about an rc?
07:04 <@mig5> yes please do merge that in, i have heard a number of people add those indexes themselves and report good results
07:05 <@mig5> an rc sounds good
07:05 <@mig5> i would like to fix this http://drupal.org/node/1004526
07:05 <@mig5> this functionality got ripped out for some reason in like, June
07:05 <@mig5> so it's not critical, but i hate seeing good work disappear
07:05 <@anarcat> ah
07:05 <@anarcat> yeah, agreed
07:06 <@mig5> i'll briefly run through what i've been doing in the last 48 hours
07:06 <@mig5> i've mainly been trying to stabilise a bunch of shit
07:06 <@mig5> You could create platforms and servers with the same names/hostnames, leading to Duplicate entries and context clashes
07:06 <@mig5> http://drupal.org/node/1039010 
              http://git.aegirproject.org/?p=hostmaster.git;a=commitdiff;h=772cd8c2b5e...
07:07 <@mig5> Drush 4.x is broken in terms of rsyncing stuff to remote servers, so I reverted HEAD to use 3.3. see http://drupal.org/node/1041386
07:07 <@mig5> Drush Make beta10 is broken re: remote makefile referencing. So upped to beta11. http://drupal.org/node/979656
07:07 <@mig5> committed that fix for that Quota bug: http://drupal.org/node/1003666
07:07 <@mig5> Some deprecated ereg_replace thing in provision
07:07 <@mig5> uid 1 was not mapped to client 1 in hosting_client_user which broke some client-based platform access control http://drupal.org/node/996578
07:08 <@mig5> unconed identified an infinite loop with provision-save and contexts: http://community.aegirproject.org/node/267
07:08 <@mig5> I couldn't reproduce the infinite loop but can confirm clusters simply don't work
07:08 <@anarcat> about that uid1 thing - i thought uid1 was bypassing all access checks?
07:08 <@anarcat> i think ergonlogic had problems with that in the past too
07:08 <@anarcat> i see
07:08 <@mig5> it *was* at some point
07:08 <@anarcat> it'd be nice that node/267 be reported as a real bug...
07:08 <@mig5> but i decided, if we are letting people check a box granting access to that user, then maybe it should just work as expected
07:08 <@anarcat> too bad ppl report issues on community.a.o
07:08 <@anarcat> agreed
07:08 <@mig5> if it bypasses the checks, it should probably not even be a checklist option, 
07:08 <@mig5> so i just fixed it the other way
07:08  * anarcat nods
07:08 <@anarcat> ok
07:09 <@mig5> yes unconed, He supplied me with a patch that seems to fix clusters! but concerned that I still couldn't reproduce the infinite loop.
07:09 <@mig5> xk has similar issues, so I put the patch there for review: http://drupal.org/node/1016890
07:09 <@anarcat> cool
07:09 <@mig5> and finally that Aliases thing
07:09 <@mig5> (phew! yes i did take notes in preparation for this scrum :)
07:09 <@mig5> that's me done
07:09 <@anarcat> man you're awesome
07:09 <@anarcat> do you plan to be as awesome next week? ;)
07:10 <@mig5> i can try, but i might balance it out by throwing in some migressions
07:10 <@mig5> :)
07:10 < eft_> my efforts are barely worth mentioning
07:10 < eft_> I didn't mention last week that I contributed a small wiki : using drush_make to optimize workflow http://community.aegirproject.org/node/256
07:11 <@mig5> eft_: yes, nice article!
07:11 <@anarcat> mig5: excellent :)
07:11 <@anarcat> okay, anyone else has anything to add?
07:11 <@anarcat> anybody scared of an RC?
07:11 <+omega8cc> This week (well, in the last minute) I rewrote and finally submitted for review two commits: one to add Nginx related how-to in the docs/INSTALL.txt - http://drupal.org/node/1042402 and second (too big probably, sorry!) with many improvements for Nginx configuration templates: http://drupal.org/node/1042312. I promise to submit future changes in the small incremental chunks instead of one big update. Next week I plan to submit even more Nginx related improv
07:11 <+omega8cc> and will debug mysterious issue - Aegir fails to rewrite paths in the "files" table on second and next site rename tasks, it works only on the first rename and I reproduced it on more than 5 imported sites, so something for sure interesting to debug and submit a patch (I hope). Also, I plan to finally work on some multiserver deployments and hope to help to find a fix for Drush 4.1 - http://drupal.org/node/1041386. That is it from me.
07:12 <@anarcat> omega8cc: your first line was stripped
07:12 <@anarcat> at Nginx related improv
07:12 <@mig5> nice, yes i freaked out the other day not knowing how to set up aegir with just nginx :) so those docs would be great
07:12 <@anarcat> thanks omega8cc ! :)
07:13 <@anarcat> your work is really appreciated, i wonder if we shouldn't just commit the huge patch with the hope that next ones will be incremental :)
07:13 <@anarcat> esp. considering you also use git, you should really "commit often" :)
07:13 <@anarcat> okay, anybody else?
07:13 <@mig5> anRC would be great - either way, yes definitely a new release, there are some annoying and critical bugs in beta2 (the data loss multiserver one for one)
07:13 < eft_> any word from devseed on moving c.a.o. ?
07:13 <@mig5> oh yes. or a.o
07:14 <@mig5> does anyone want to work on a drupalised version of a.o? and maybe give it to anarcat to host (or i can host it)
07:14 <@mig5> i can't theme for shit, so I'm out :)
07:14 < eft_> how much is there?
07:14 <@anarcat> mig5: i don't think we should drupalize a.o, actually
07:14 <@mig5> ah, cool that's fine with me
07:14 <@anarcat> just leave it like this, but remove the time-changing stuff
07:14 <@anarcat> and yeah we can host it
07:14 <@mig5> i remember adrian mentioning it
07:15 <@anarcat> oh, the DNS transfer of a.o and .com is stuck
07:15 <@mig5> everyone is annoyed at the g.d.o link, so if we could change that at least
07:15 <@mig5> ah
07:15 <@anarcat> email problems between gandi and devseed
07:15 <@anarcat> yeah
07:15 <@anarcat> but they wanted to transfer ownership of the domains too
07:15 <@anarcat> and i started the xfer
07:15 <@mig5> oh i see
07:16 <@anarcat> but anyways, yeah, transfer the NS and we'll go ahead from there
07:16 <@anarcat> okay, that's it for the scrum folks, thanks for attendign!
07:16  * anarcat heading for a sandwich
07:16 <@mig5> cheers
07:16 < eft_> later

06:59 <@anarcat> scrum time!
06:59 <@anarcat> mig5: you there?
06:59 <@mig5> yep
06:59 <@anarcat> omega8cc / ergonlogic / others... scrum starts now
06:59 <@anarcat> mig5: you wanna start?
06:59 <@anarcat> need to remove my skis
07:00 <@mig5> ok
07:00 <@mig5> i haven't done much, i still would like testers of http://drupal.org/node/1004526
07:00 <@mig5> but it sounds like we have two different issues there
07:00 <@mig5> and that i misunderstood the first issue
07:01 <@mig5> drush 4 remains unusable at least for multiserver, i had some difficulty convincing the drush guys that it was their problem http://drupal.org/node/1041386
07:01 <@anarcat> i wanted to test that and http://drupal.org/node/1016890 for ya before the RC
07:01 <@mig5> yes it's that cluster thing and the aliases that would be nice to get in before the RC
07:01 <@mig5> oh
07:02 <@mig5> and the package indexes
07:02 <@mig5> which i confirmed did seem to speed things up even on my tiny system
07:02 <@mig5> so do go ahead and merge that
07:02 <@mig5> that's all from me I think :s
07:02 <@anarcat> okay
07:02 <@anarcat> i can take a look at the drush 4 issue
07:03 <@anarcat> they are correct that the API is not supposed to change in dr4
07:03 <@anarcat> so if it's a dr bug, we'll have to wait until dr5 for a fix
07:03 <@mig5> yeah, on the other hand, they have completely reversed the logic
07:03 <@mig5> mmm.
07:03 <@anarcat> which is fine because dr5 is coming soon
07:03 <@mig5> o rly. fair enough!
07:03 <@anarcat> i'll weigh in on that one and we'll see
07:03 <@anarcat> on my side
07:03 <@anarcat> i haven't done much. :)
07:03 <@anarcat> still swamped with internal work here
07:04 <@anarcat> i wanted to do an RC, but failed to find time, i have scheduled time to review patches and do the RC on monday
07:04 <@mig5> oh nice, thanks
07:04 <@anarcat> maybe we should stick with 3.3 for aegir 4
07:04 <@anarcat> if you want to take care of the release before that, that's fine with me too though :)
07:04 <@anarcat> otherwise well i opened a few crazy issues
07:05 <@mig5> oh i need to try and reproduce omega8cc's report here: http://drupal.org/node/1047922 . not sure that's drush 4's fault, unless we know it works fine on 
              3.3 too
07:05 <@anarcat> most notably the exportable backup and wordpress support craziness
07:05 <@mig5> haha
07:06 <@anarcat> also, we have migrated to koumbit's DNS servers so i can do DNS changes if people need that to happen from now on
07:06 <@anarcat> api.aegirproject.org is up
07:06 <@anarcat> and aegirproject.org has been fixed
07:06 <@mig5> awesome stuff
07:07 <@anarcat> i think this is it for me too, i'm getting more and more towards freeing up my time to work on aegir, and we are aiming to work on our internal roadmap
                 'real soon' here at koumbit
07:07 <@anarcat> anybody else wants to cue in?
07:08 <@anarcat> anybody else is awake? :)
07:09 <@anarcat> so i guess this just makes for a short scrum! :)
07:09 <@mig5> no problem - i can go back to bed :)
07:10 < kvanderw> anarcat: what is a scrum? and could dummies help?
07:10 <@anarcat> thank you all
07:11 <@anarcat> kvanderw: http://community.aegirproject.org/scrums

07:00 <@anarcat> aaaalright
07:00 <@anarcat> hellow everybodyyy!
07:00 <@anarcat> welcome to our weekly scrums
07:00 <@anarcat> (we need a bot for that cheering crap - anyways)
07:00 <@anarcat> i
07:00 <@anarcat> have done nothing again. :P
07:00 <@anarcat> actually, that's not true
07:00 <@anarcat> i have done a good review of the queue
07:00 <@anarcat> to try to prepare for the RC
07:01 <@anarcat> committed a bunch of things lying around
07:01 <@mig5> you've done great
07:01 <@anarcat> and then univate decided to submit a bunch of patches on top of that, so i'll have to start all over again
07:01 <@anarcat> univate: thanks ;)
07:01 <@anarcat> yeah, it's been good
07:01 <@anarcat> i still have to review my own internal aegir shit before we go towards a release
07:01 <@anarcat> we have around 200+ issues in our internal queue, it's a mess
07:02 <@anarcat> we had a marketing meeting today where we determined our priorities, but i am not sure i should talk about that now ;)
07:02 <@mig5> :)
07:02 <@anarcat> expect another announce soon
07:02 <@anarcat> we are in talks with devseed to migrate the OA site (community.a.o) to Koumbit (? or mig5 ?) THIS MONDAY!
07:03 <@anarcat> so consider this the first announcement:
07:03 <@anarcat> ON MONDAY, 16H EST, the community site will go down for a migration
07:03 <@anarcat> (that's about the same time as now +1h)
07:03 <@anarcat> i still hope that we can RC next week, which will mean creating the 0.4.x branch
07:04 <@anarcat> but before that, i want to do some tests on my side and review our queue
07:04 <@anarcat> we had a weird issue with cron not running on a site here, that i have trouble making a diagnostic of
07:04 <@anarcat> with that
07:04 <@anarcat> i think i am done, mig5 ?
07:04 <@mig5> ok
07:04 <@mig5> not much to report, other than i think the only real blocker to getting an rc out, is that the upgrade path is broken
07:05 <@mig5> http://drupal.org/node/1056864
07:05 <@anarcat> i was scared to read that issue
07:05 <@mig5> i really need to speak to unconed about this since it's his patch, 
07:05 <@mig5> and only he understands it, it's like talking to another Vertice :)
07:06 <@anarcat> good good :)
07:06 <@mig5> that's really all from me :s
07:06 <@anarcat> plans for next week?
07:06 <@mig5> to try and fix that, I suppose
07:06 <@anarcat> cool
07:07 <@anarcat> (as an aside, we just found this code in /var/aegir/fuck.php on our prod server, before destroying it, i pastebin'd it in the idea it might be useful for others: http://pastebin.com/163byC1z)
07:07 <@anarcat> (i am not sure what it does)
07:07 <@mig5> wtf
07:07 <@anarcat> okay, anyone else?
07:07 <+omega8cc> Last week I worked on some new features in the Nginx for Aegir configuration, like improved caching and performance (patches to be submitted), and tested everything with Drush 4 and 5 (head)
07:07 <+omega8cc> Now still working on issues like http://drupal.org/node/1056864, and hope to fix more Drush related issues next week to get Aegir Drush 4 compatible. That is it from me :)
07:08 <@anarcat> adrinux / darthsteven / EclipseGc / ergonlogic / grugnog_ / mvc / sfyn / skwashd / univate : you're all aegir contributors and welcome to say hi during this scrum - what you're working on these days... etc
07:08 <@anarcat> thanks omega8cc !
07:08 <+darthsteven> Sure...
07:08 <@mig5> oh yeas darthsteven wrote some killer docs :)
07:08 <+darthsteven> I added the first part if some docs about context
07:09 <+darthsteven> More to follow, and extra docs about services too
07:09 <+EclipseGc> anarcat: oh awesome
07:09 <+darthsteven> That's it from me
07:09 <@anarcat> thanks darthsteven
07:10 <+EclipseGc> all of my time these days has been devoted to non-aegir-specific Drupal 7 work these days, though I do see a number of potential point of collaboration on various items in D7 for whenever aegir decides to make that jump
07:10 <@anarcat> EclipseGc: have you done d6 to d7 porting work?
07:10 <@anarcat> would you be interested in contributing to that?
07:11 <+EclipseGc> anarcat: I've worked on ctools/page_manager porting to D7 yes, as well as my own context_admin
07:11 <@anarcat> how's that going? :)
07:12 <+EclipseGc> anarcat: very good all things considered, native support for all entity types in page_manager is a pretty freaking awesome thing
07:12 <@anarcat> :)
07:12 <@anarcat> alright
07:12 <@anarcat> thank you EclipseGc
07:12 <@anarcat> anyone else has anything to add to this mighty scrum?
07:13 <+EclipseGc> anarcat: from an aegir perspective, (as an example) if say, "site nodes" became "site entities" in the D7 version, we could still utilize panels to display the site information (not that we're doing that now, but it is a possibility)
07:13 <@anarcat> oh, an idea i had: we should have a "wildcard domains" variable in the frontend for wildcards pointing to the aegir server while we fix DNS, then when people create sites, they can just type the left part of the domain and choose the wildcard from a dropdown
07:13 <@anarcat> EclipseGc: right, ok
07:13 <@anarcat> EclipseGc: should we wait for d7 before creating the "dns zone" content-type for example?
07:13 <@anarcat> how easy is it to declare entities programmatically?
07:14 <@anarcat> anyways, i have to head out now, so thanks everyone for attending, and have a nice day
07:14 <+EclipseGc> anarcat: well, the only way to declare an entity is programatically, there's no... entity ui or anything that allows you to build new entities
07:14 <@anarcat> can anyone take care of uploading this to the community site?
07:14 <@anarcat> EclipseGc: ok
07:14 <+EclipseGc> anarcat: thus far, a new entity, front to back all manual is minimum about 400 lines of code if you want it to be fairly usable
07:15 <@mig5> yeah i'll sort it later
07:15 <@anarcat> EclipseGc: ow?
07:15 <+EclipseGc> anarcat: I'm hoping that fago's entity_api and ctools can have a meeting of the minds and do something really great to make all of that (including user interfaces) much easier
07:16 <+EclipseGc> but that is still non-existent yet, and many people are uncomfortable depending on entity_api at the moment (though I hear it cuts down on the necessary code for an entity significantly)
07:16 <@anarcat> aand how easy is it to port existing content types to that ... stuff?
07:16 <+EclipseGc> anarcat: I'm going to change your vocabulary real quick (if you don't mind) just so there's no confusion
07:17 <@anarcat> i really have to head out, but feel free, i'll read on later tonight
07:17 <@anarcat> ciao everyone
07:17 <+EclipseGc> anarcat: "content types" or what we call node types in D6 and below are actually "bundles" (generic term) of the node entity now.  You can still call them whatever you like, but to be precise I usually say "node bundles".  All entity types can have bundles
07:18 <@anarcat> fuck
07:18 <@anarcat> sorry, screwed up there
07:18 <@anarcat> EclipseGc: got it :)
07:18 <@anarcat> ciao for real
07:18 <+omega8cc> cia
07:18 <+omega8cc> o
07:18 <+omega8cc> :)

07:00 <@anarcat> so welcome to our weekly scrum
07:01 -!- JoshBenner_ [~quassel@pool-173-59-14-26.phlapa.fios.verizon.net] has joined #aegir
07:01 <@anarcat> so to start with - i had a major fuckup with the community site with a verify that went bad
07:01 <@anarcat> because the alias didn't have the profile set in
07:01 <@anarcat> i documented all this in here http://community.aegirproject.org/node/355
07:01 <@mig5> reading that now. why did oyu need to manually run provision-deploy rather than standard migrate?
07:02 <@anarcat> mig5: because the site wasn't in aegir at first
07:02 <@mig5> gotcha
07:02 <@anarcat> i was importing from devseed
07:02 <@mig5> oh ofcourse *slaps forehead*
07:02 <@anarcat> maybe i should clarify that.. but anyways
07:02 <@mig5> no i'm just a dick and just woke up :)
07:02 <@anarcat> other than that, this week i have struggled with the issue queue
07:02 <@mig5> +1...
07:03 <@anarcat> specificall with that eugene guy which apparently decided we were evil and decided to develop his own stuff privately and stop collaborating on the queue
07:03 <@anarcat> i wrote a response in the issue queue, but i wanted to share here that it pissed me off real bad to hear somebody just go away like this because we're not being nice enough
07:03 <@anarcat> when he's treating us with abuse and duplicate issues
07:04 <@anarcat> hopefully he will not come back to the queue but share his work with others so that we don't reinvent the wheel
07:04 <@anarcat> one of those duplicate issues is this: http://drupal.org/node/1058918
07:05 <@mig5> his hosting_folders feature was just wrong anyway
07:05 <@anarcat> apparently eugene had a contrib module to fix this, but because i marked his issue as duplicate of mine, he got angry and removed his code from github
07:05 <@anarcat> but anyways, we talked about this vhost customization thing, and people were suggesting that it should be in contrib, but i feel like i disagree - if it's safe, it could be in core couldn't it?
07:05 <@mig5> the subfolder stuff?
07:06 <@anarcat> no no
07:06 <@anarcat> http://drupal.org/node/1058918
07:06 <@anarcat> the custom vhost stuff
07:06 <@mig5> ah
07:06 <+omega8cc> in core, imo
07:06 <@anarcat> right
07:06 < eft_> anarcat: that's moving vhost config  into front end?
07:07 -!- Artusamak is now known as Artusamak_afk
07:07 <@anarcat> so anyways, that's about it for me - i'll try to work more on the issue queue and make an RC during next week unless there are objections here
07:07 <@anarcat> eft_: no
07:07 <@anarcat> mig5: next!
07:07 < eft_> anarcat: that's great that you migrated c.a.o. - do we still need the 1700 EST downtime in the header of this channel
07:07 <@anarcat> eft_: no
07:07 -!- anarcat changed the topic of #aegir to: Aegir hosting system 0.4-beta2 released! http://community.aegirproject.org/0.4-beta2 | Issue queue: http://is.gd/edalY | read this before asking: http://community.aegirproject.org/bugs | scrums on thursdays 2000UTC
07:08 <@mig5> i've done nothing all week due to some hectic work and basically some of our users killing my love for the project.
07:08 <@mig5> i fixed a minor bug here or there
07:08 <@mig5> and will likewise attack the queue some more, i think we should rc soonor we'll just be forever trying to battle that
07:08 <@anarcat> yeah
07:08 <@anarcat> agreed
07:09 <@mig5> that's it from me
07:09 <@anarcat> seems like the only blocker is the ssl rollback, which we could roll into another rc
07:09  * eft_ wishes he had more to offer than nitpicks about channel headers
07:09 -!- Artusamak_afk is now known as Artusamak
07:09 <@anarcat> let's just RC the fucking thing
07:09 <@anarcat> mig5: if you feel like it - just do it, and ignore the issue queue ;)
07:09 < eft_> mig5: any progress on your workflow diags?
07:09 <@anarcat> eft_: you can fight with trolls in the issue queue and get them off our backs :)
07:09 <+omega8cc> go with RC - to avoid "one more thing" syndrome == release 3 years later ;)
07:09 <@anarcat> there's a lot of triage work that is needed in the queue, that mostly anyone could do
07:09 <@mig5> eft_: that was just for a client proposal, it wasn't very good, http://greenbeedigital.com.au/files/aegir_workflow.jpg
07:10 <@anarcat> mig5: anything else?
07:10 <@mig5> anarcat: nope, that's it, i might release today then if i get time
07:10 < eft_> anarcat: bon cop, bad cop
07:10 <@anarcat> eft_: ouaip :)
07:10 <@anarcat> Vertice / adrinux / darthsteven / grugnog / mvc / omega8cc / sfyn / ergonlogic / univate_: anybody else got something to add to our scrum?
07:10 <@anarcat> mig5: that would be just amazing :)
07:10 <+omega8cc> not much from me this week, I only made barracuda/octopus compatible with Debian 6 and Ubuntu 10.10 plus some new fixes for Nginx config
07:11 <@anarcat> okay, anyone else?
07:11 <+ergonlogic> nothing from me
07:11 <+omega8cc> hope to work on contrib module for solr cores automatic setup - integrated with skwashd work
07:11 <@anarcat> univate_: thanks for those patches, btw, keep em coming!
07:11 <@anarcat> omega8cc: that would be freakin awesome!
07:12 <@anarcat> omega8cc: we got config for secure multi-core setups if you're interested... in our wiki
07:12 <+omega8cc> yep
07:12 <@mig5> anarcat: would love a review of http://drupal.org/node/1005014
07:12 <@mig5> (re:univate)
07:12 <@anarcat> mig5: got it, maybe tomorrow
07:12 <@anarcat> mig5: but don't wait for this to rc
07:12 <@mig5> ok
07:12 <+omega8cc> anarcat: I will check that, thanks!
07:12 <@anarcat> okay, anyone else?
07:13 <+ergonlogic> now that community.aegirproject.org is hosted at Koumbit, I could help if there's any issues with the site itself
07:13 <+ergonlogic> just let me know
07:13 <@mig5> eft_: wanted thesession_timeout something or other to be raised
07:13 <@mig5> so that it remembers you're loged in
07:13 <@mig5> logged* bah.
07:13 <@anarcat> ergonlogic: yeah, i think mig5 had issues with some images you could help with
07:13 <@anarcat> mig5: ^?
07:14 <@mig5> which images?
07:14 <@anarcat> mig5: i don't recall
07:14 <@anarcat> istr there was some thumbnail problem... wasn't there?
07:14 <@mig5> oh yes
07:14 < eft_> yea
07:14 <@mig5> possibly an atrium bug or something weird
07:14 <@anarcat> yeah
07:14 <@mig5> http://community.aegirproject.org/node/76
07:14 <@anarcat> well now we have root, so let us know what we need to do :)
07:14 <@mig5> the href to that is the full size image, but it *always* loads the thumbnail
07:14 <@anarcat> ergonlogic can take care of it or i can help
07:14 <+ergonlogic> ok, I'll take a look
07:15 <@anarcat> okay, i gotta go
07:15 <@anarcat> and the scrum is over, thanks for attending, people!
07:15 <@anarcat> and have a nice day
07:15 <@mig5> cheers
07:15 <+ergonlogic> thanks all
07:15 < eft_> ciao
07:15 <+omega8cc> ciao

09:01 <@anarcat> mig5: hey
09:01 <@mig5> up for scrum or inconvenient time?
09:01 <@anarcat> i can't believe i can't find those revisionsw http://drupal.org/node/1068280#comment-4131534
09:01 <@anarcat> hey, scrum time, look at that
09:01 <@anarcat> sure
09:01 <@anarcat> at a session here, but it still works :)
09:01 <@mig5> alright, go! :)
09:02 <@mig5> actually
09:02 <@mig5> first, i believe i saw you mention that this scrum time is inconvenient for you 
09:02 <@anarcat> did something fuckup on d.o or something?
09:02 <@mig5> drupalcon aside
09:02 <@mig5> anarcat: you'll have to be more specific about d.o fuckups :)
09:02 <@anarcat> every first wednesday of the month i have a meeting during this scrum
09:02 <@mig5> ah. let's move it then
09:03 <@anarcat> what's convenient for ya?
09:03 <@mig5> the following day, but i think that's when it used to be for you
09:04 <@mig5> and you couldn't do later
09:04 <@anarcat> right
09:04 <@anarcat> that is correct
09:04 <@mig5> so maybe we go earlier in the week
09:04 <@anarcat> yeah, i can do the day before or before before
09:04 <@mig5> let's do day before, so Wednesday for us, unless it's a problem for univate
09:04 <@anarcat> got it
09:04 <@mig5> anyway!
09:04 <@anarcat> tuesday for us
09:04 <@mig5> d.o issues?
09:04 <@anarcat> right
09:05 <@anarcat> so about the upgrade path
09:05 <@anarcat> http://drupal.org/node/1068280#comment-4131534
09:05 <@mig5> i noticed i committed a change to provision and all my old commits are still unattributed to my user account. yay
09:05 <@anarcat> that comment refers to two patches that are supposedly on head
09:05 <@anarcat> and that i can't find
09:05 <@mig5> hmm
09:05 <@mig5> they're in master aren't they?
09:05 <@anarcat> i can't find them
09:05 <@anarcat> git fetch
09:06 <@anarcat> git show f64487706638
09:06 <@anarcat> fatal: ambiguous argument 'f64487706638': unknown revision or path not in the working tree.
09:06 <@mig5> http://drupalcode.org/project/hostmaster.git/commitdiff/75191804926c5c29...
09:06 <@mig5> http://drupalcode.org/project/hostmaster.git/commitdiff/a8dfee3391cb89f0...
09:06 <@mig5> are you sure your origin is not git.aegirproject.org ? :)
09:06 <@anarcat> um
09:07 <@anarcat> well
09:07 <@anarcat> those are not the commits i am looking for
09:07 <@mig5> oh
09:07 <@anarcat> that above comment refers to two other commits
09:07 <@mig5> oh oops
09:08 <@mig5> yeah i don't see it
09:08 <@mig5> weird
09:08 <@anarcat> oh well
09:08 <@anarcat> maybe i didn't push them and it works anyways... (?!)
09:08 <@anarcat> anywho
09:08 <@anarcat> so i wanted to merge shit in and release rc2 this week
09:09 <@anarcat> i talked to a bunch of people here at drupalcon about aegir
09:09 <@anarcat> i just did a aegir 101 session to about 20 people
09:09 <@mig5> nice
09:09 <@mig5> how'd that go
09:10 <@anarcat> pretty well
09:10 <@anarcat> people didn't really *want* to install aegir so that part didn't really work
09:10 <@anarcat> but we had good exchanges and dispelled common myths
09:10 <@anarcat> and gave away cool stickers :)
09:10 <@anarcat> we have a roadmap session planned for tomorrow
09:10 <@anarcat> at 2, in missouri again
09:10 <@anarcat> and then we are thinking of having a doc/code sprint on friday
09:11 <@mig5> nice
09:11 <@anarcat> maybe help people out writing drush extensions, and a bunch of other ideas
09:11 <@mig5> we have about 20 'for reviews' in the queues
09:11 <@anarcat> yeah
09:11 <@mig5> mostly eugen :P
09:11 <@anarcat> i'll try to throw people at those
09:11 <@anarcat> we may have new people to get into the project
09:11 <@mig5> excellent
09:11 <@anarcat> i met with shrop, EclipseGc and others
09:11 <@anarcat> what else
09:12 <@anarcat> i want to release rc2 :P
09:12 <@mig5> well - you can, i didn't see any errors doing an upgrade to master from 0.3
09:12 <@anarcat> i was hoping someone could shed light on this - but maybe i'll just do it myself: http://drupal.org/node/1081528
09:12 <@mig5> regardless of that missing commit
09:12 <@anarcat> oh, and i have pushed 6.x-1.x as the stable branch
09:12 <@anarcat> for provision
09:13 <@mig5> yeah that sounds expected: drupal keeps those paths in the db, you need to cache clear before it fixes itself up, so your theory is probably right there
09:13 <@mig5> that would happen with or without a Migrate task, basically
09:13 <@mig5> but would be nice for Migrate to fix it
09:13 <@anarcat> and for hostmaster now
09:13 <@anarcat> cool
09:14 <@anarcat> so i'll look at that before the release
09:14 < shrop> anarcat: you have aegir stickers?
09:14 < shrop> that would be cool
09:14 <@anarcat> shrop: yes!
09:14 <@anarcat> of course :)
09:14 < shrop> ok.. want one tomorrow at the meetup if you have any.. :)
09:14 <@anarcat> come to the bof tomorrow :)
09:14 <@anarcat> of course
09:14 < shrop> will do
09:14 <@anarcat> alright
09:14 <@anarcat> so what else for the scrum
09:14 <@anarcat> we did a little spike on the install docs manual for the purpose of the session
09:15 <@anarcat> i'd actually like to get a debian package working for rc2, but i'm not sure i'll have time to do this
09:15 <@anarcat> ideally, we'd get rc2 out during that code sprint
09:15 <@mig5> maybe for 1.0 :)
09:15 <@anarcat> ok, i think that's it for me
09:16 <@anarcat> well, i'd like the package to be tested :)
09:16 <@mig5> i've got nothing to report. univate, you here?
09:16 <@mig5> omega8cc?
09:16 < univate> hey
09:16 < hefring> eh oh
09:17 <@mig5> did you want to add anything to the scrum?
09:17 <@anarcat> mig5: i have merged the two commits you mentionned on the stable branch
09:18 <@mig5> cheers
09:19 <@anarcat> and then some more
09:19 <@mig5> i dont fully understand omega8cc's patches here http://drupal.org/node/949044#comment-4144944
09:19 <@mig5> +  $form_state['values']['parameters']['new_uri'] = $url; // force lowercase
09:19 <@mig5> does that variable assignment really force lowercase?
09:20 <@mig5> maybe it's for readability.
09:20 <@mig5> anyway
09:21 <@anarcat> that doesn't force lowercase
09:21 <@anarcat> at all
09:22 <@anarcat> otherwise, i think that's it for our scrum
09:23 <@mig5> yep
09:23 <@mig5> thanks all

09:01 <@anarcat> alright
09:01 <@anarcat> scrum time
09:01 <@anarcat> mig5 / univate / Vertice / darthsteven / mvc / omega8cc : scrum time
09:01 <+omega8cc> hello!
09:01 < hefring> que tal
09:01 <@mig5> morning
09:01 <+darthsteven> Hello!
09:01 < hefring> hello
09:01 <@anarcat> ghankstef / mrbaileys / sfyn_ / shrop / / others i forgot: welcome to our weekly scrum! feel free to jump in!
09:02 <@anarcat> so welcome everybody
09:02 <@anarcat> we're back from drupalcon! it was an insane week
09:02 <@anarcat> so i'll start with that
09:02 <@anarcat> crazy
09:02 <@anarcat> week
09:02 <+omega8cc> and sk]washd!
09:02 <@anarcat> met a bunch of people
09:02 <@anarcat> oh yeah! skwashd !
09:02 <@anarcat> even though we didn't have a formal aegir session schedule (which is strange considering there were 5 submitted), we did host 2 bofs and a training session, plus a code sprint
09:03 <@anarcat> i met with about 30-40 people to talk about aegir during those session
09:03 <@mig5> someone must've been anti-aegir on the organising committee :)
09:03 <@anarcat> for me the best session was the roadmap session, of which my coworker mvc posted a summary here: http://community.aegirproject.org/node/488
09:03 < skwashd> anarcat, we should've had 34 at the initimate session alone :)
09:03 <@anarcat> mig5: i actually suspect it's because there weren't "big names" submitting a session
09:04 <@anarcat> skwashd: that's right!
09:04 <@mig5> ah ;)
09:04 <@anarcat> and i was late to the intimate aegir session, which sucked, but it was my only "free" day during the whole week
09:04 <@anarcat> koumbit *drove* to chicago, which was insane
09:04 <@anarcat> 1400km one way, so around 3000 km of driving, 30h total...
09:04 <@anarcat> lots of fun and spilled coffee
09:04 <@anarcat> oh and i scratch the fucking car when parking it in a narrow street
09:05 <@anarcat> 4500$CAD in damage, believe it or not
09:05 <@anarcat> lots of fun
09:05 <@anarcat> anyways
09:05 <@mig5> haha
09:05 <@anarcat> so we're passing the hat to pay for the stupid koumbit van ... ;) (kdding)
09:05 <@anarcat> we *almost* got rc2 released
09:05 <@anarcat> i was about to push the tags when they cut off power and wifi in the code sprint
09:05 <@anarcat> but mig5 ended up doing the last mile on that
09:06 <@mig5> sort of
09:06 <@anarcat> i personnally met with shrop, cashwilliams, ghankstef, joestewart, and probably others i forget here :)
09:06 <@anarcat> i feel that our presence there got people interested in participating in the project and i got that objective at least partially accomplished
09:07 <@anarcat> with people comitting to watching and helping in the queues, and i helped people review patches in the code sprint
09:07 <@mig5> it sounded like it had a better bof/community spirit than san francisco
09:07 <@mig5> which is excellent
09:07 <@anarcat> yeah
09:07 <@anarcat> we did more BOFs
09:07 <@anarcat> i think it's better for us to do BOFs than formal sessions - people know of aegir, we need to make it work now :)
09:08 <@anarcat> i closed 10-20 tickets in the issue queue and pissed of eugen again
09:08  * mig5 claps
09:08 <@anarcat> we're down to around 5-10 needs review tickets
09:08 < ghankstef> it works  great  -  except for when it doesn;t  : )  but when it does its really really great
09:08 <@anarcat> this week i am working from home so i am hoping to get more aegir work done than usual
09:08 <@anarcat> but so far i'm failing, mostly because of internal poutine again
09:09 <@mig5> you've got chips and gravy inside you?
09:09 <@mig5> :)
09:09 <@anarcat> i hope to get into it tomorrow and get a solid 3 days
09:09 <@anarcat> haha
09:09 <@anarcat> i mean internal to koumbit :P
09:09 <@mig5> :)
09:09 <@anarcat> and it's french fries and gravy and cheese, for your information :)
09:09 <@anarcat> but enough with quebecois cuisine
09:09 <@anarcat> i think i'm done when i start to talk about poutine :)
09:09 <@anarcat> ah, yeah
09:10 <@anarcat> this week i hope to get working on "i want to run drush on my sites as a regular user"
09:10 <@anarcat> which promises to be a real PITA
09:10 <@anarcat> and also working on the 2.x roadmap, after feedback from the community
09:10 <@anarcat> so that's it for me - next!
09:11 <@mig5> i did nothing except push out rc2, which went horribly wrong, but mostly works
09:11 <@mig5> next! :)
09:11 <@anarcat> haha
09:11 <@anarcat> a bit more on that though - we weren't able to tag hostmaster, because of a bug on d.o
09:11 <@anarcat> we're pushing the limits on git and install profiles on d.o, and that's cool for those people, they like us :)
09:11 <@anarcat> everybody is quite happy and proud that aegir is back on d.o
09:11 <@anarcat> if feels good
09:11 <@anarcat> ah and for everyone that contributed to aegir here:
09:12 <@anarcat> i had a *lot* of thanks and good feedback on the project
09:12 <@anarcat> people *love* aegir
09:12 <@anarcat> they are very grateful and thank me for my involvement
09:12 <@anarcat> so i want to share that with the team here
09:12 <@anarcat> because i couldn't possibly have done this alone, so you all share this credit :)
09:12 <@anarcat> mig5: you really should have been there :)
09:13 <@mig5> i doubt i'll ever make another drupalcon
09:13 <@mig5> the two times of the year are awful for me frankly
09:13 <@mig5> anyways
09:13 <@anarcat> that's too bad
09:13 <@mig5> i'll look at that core dump/segfault issue you're having
09:13 <@mig5> i have never reproduced it
09:13 <@anarcat> you don't *have* to come twice a year :)
09:13 <@mig5> but i feel i understand the *reason* for unconed's patch
09:13 <@anarcat> if you have xdebug enabled, it's not a core dump, it's a loop
09:13 <@mig5> right
09:14 <@mig5> but i've never seen the segfault myself, is what i mean
09:14 <@anarcat> yeah
09:14 <@anarcat> you need to reference a non-existing platform
09:14 <@mig5> unconed explained it was something about the stdin context in drush that caused a loop of loading the @self or @server_msater alias
09:14 <@mig5> ahy
09:14 <@mig5> ah*
09:14 <@mig5> he tried to specifically exclude the @server_master context in his patch, which fixed clusters in this case, but broke install/migrate
09:14 <@mig5> anyway, that's for the tickets, i won't noise up the scrum now
09:15 <@anarcat> alright, anyone else?
09:15 <+omega8cc> I did nothing new "inside" the project last week. There are still some Nginx config improvements waiting for review in the queue, but..
09:15 <+omega8cc> I released Barracuda and Octopus 1.0-boa-T to celebrate Aegir 1.0-rc2, which introduces support for Squeeze and Maverick, with even more speed improvements, so..
09:16 <+omega8cc> I *think* we are already as fast as Mercury (formerly Pantheon) out of the box ;) Seriously, it needs some testing to confirm. That is it from me!
09:16 <@anarcat> alright!
09:16 <@anarcat> people looking for low-hanging fruits!
09:16 <@anarcat> **** THIS IS YOU! ****
09:16 <@anarcat> http://drupal.org/project/issues?text=&projects=provision,+hosting,+hostslave,+eldir,+Hostmaster+(Aegir)&status=8&priorities=All&categories=All
09:16 <@anarcat> this is the "needs review" queue
09:17 <@anarcat> what you need to do in there is to pick an issue in there, try to reproduce the issue described
09:17 <@anarcat> if you can't reproduce, close the issue (can't reproduce)
9:17 <@anarcat> if you can, try to apply the patch to see if it fixes the thing for you, if it does mark it RTBC (ready to be committed), if not, "needs work"
09:17 <@anarcat> there is also work to be done in the documentation
09:18 <@anarcat> we have reworked the manual, actually ergonlogic did
09:18 <@anarcat> http://community.aegirproject.org/notebook
09:19 <@anarcat> followup on documentation is in the "documentation" category in hostmaster
09:19 <@anarcat> see also http://community.aegirproject.org/node/377
09:19 <@anarcat> we specifically need help on the upgrade document
09:19 <@anarcat> and reorganising the "using aegir" section
09:19 <@anarcat> so if nobody has anything else to add
9:19 <@anarcat> i think that's it for our scrum this week
09:20 <@anarcat> thanks for everyone for attending
09:20 < ghankstef> I will have a look at the upgrade doc   see if I can add  to it
09:20 <@anarcat> ghankstef: alright!
09:20 < ghankstef> Will give me a good excuse to update an old aegir  site
09:20 < ghankstef> oh yeah its all empty
09:20 <@anarcat> well
09:21 < ghankstef> guess I can improve on that a bit
09:21 <@anarcat> it's not really empty - i feel ergonlogic forgot to update the status page
09:21 <@anarcat> it seems the UPGRADE.txt was migrated into separate wiki pages
09:21 <@mig5> the sub pages are where it's at
09:21 <@anarcat> maybe it can be merged in one page
09:21 <@mig5> the wrapper page is a bit bare
09:21 <@anarcat> i think we should throw everything in the parent page there
09:22 <+omega8cc> and the structure is too deep now
09:22 <@anarcat> alright
09:22 <@anarcat> that's it for me folks, going back in my "trying to code" hole :)
09:23 <@mig5> thanks all
09:23 <+omega8cc> thanks!

08:58 <@anarcat> alright, so we're 1 minute away from the scrum, but i'll start anyways :P
08:59 <@anarcat> i'm a bit in a rush since we're going to replace a switch at the datacenter in about an hour
08:59 <@mig5> np
08:59 <@anarcat> which could affect community.a.o momentarily
08:59 <@anarcat> we had a few issues with the server
08:59 <@anarcat> it was replaced with a spare recently and we diagnosed a problem with a corrupted bios
08:59 <@anarcat> our hw provider is running more tests and we hope to get the original server back online shortly
09:00 <@anarcat> as for actual dev
09:00 <@anarcat> i have worked on provisionacl recently and got it in good shape
09:00 <@anarcat> i hope to deploy it in production here this week and get rid of our ugly sudo -u aegir kludges we were giving to workers
09:00 < Aurorus> sounds interesting anarcat
09:00 <@anarcat> so now not only can worker access modules/ files/ etc without problems, but they can run drush commands as their regular user
09:01 <@anarcat> *plus* this gives access to the regular drush aliases
09:01 <@anarcat> although there are still warnings (fixed in drush 5 and drush 4-head)
09:01 <@anarcat> i'm working on having site aliases respect drush -i
09:01 <@anarcat> i have worked a lot on the debian packages too, they are mostly ready
09:02 < Aurorus> anarcat: Are there plans to allow the deletion of sites and platforms that fail verify?
09:02 <@anarcat> provision is packaged, and there's a meta-package for hostmaster that downloads provision
09:02 <@anarcat> i also want to get the debian packages finished this week and we'll update the docs accordingly
09:02 <@anarcat> hopefully we can ship 1.0 with debian
09:02 <@anarcat> i started coordination of the rc3 release, but we have a significant blocker with d.o that refuses to release hostmaster
09:03 <@anarcat> see http://drupal.org/node/1105824
09:03 <@anarcat> for the drush issues: http://drupal.org/node/1104450 and http://drupal.org/node/957182
09:04 <@anarcat> i am going to work more on security in the coming weeks, i plan to work two weeks in a retreat in the woods with internet access :)
09:04 <@anarcat> i will make sure we don't bootstrap evil modules so that allowing access to modules and themes is secure
09:04 <@anarcat> i'd like to release rc3 tomorrow
09:05 <@anarcat> i am thinking of starting work on the d7 port and ldap integration for 2.x during the next two weeks
09:05 <@anarcat> and koumbit has done its internal roadmap and we'll be working hard on 2.x for the summer
09:05 <@anarcat> i think that's pretty much it for me!
09:05 <@mig5> nice one. you have given yourself a lot of work as usual :)
09:05 <@anarcat> i am glad to see that crazy stuff darthsteven has been doing here :) http://www.computerminds.co.uk/articles/aegir-tasks-daemon
09:05 <@anarcat> i think it should be merged in
09:06 <@anarcat> well, if anyone wants to pick up rc3 or similar things, be my guest :)
09:06 <@mig5> i read that: i think the queue thing would be good in aegir, hopefully doesn't have too many dependencies?
09:06 <@anarcat> drush especially needs a lot of love - and we'll need to work with them for aegir 2.0, which i suspect will support only drush 5 or above
09:06 <@anarcat> mig5: seems to be standalone contrib!
09:06 <@mig5> ok cool
09:06 <@anarcat> it's just a ghetto php daemon :)
09:06 <@anarcat> what Vertice didn't want :)
09:06 <@mig5> i thought it deopeneded on some obscure launchd-like OSX daemon
09:07 <@mig5> but i admit i didn't read it thoroughly
09:07 <@anarcat> darthsteven: recommends supervisor, but it's just to keep the php script alive - you could use whatever you want
09:07 <@anarcat> hey, we could even use the cronjob to restart the daemon if it fails
09:07 <@mig5> anyway: not much from me, as usual. i basically encountered some significant stability issues with the master branch, and fixed it as best as I could, though I worry i broke some of your ideas there. http://drupal.org/node/1106768
09:08 <@mig5> i found the bug while writing my aegir build test in jenkins, which was exactly what it was designed to do (although it didn't literally fail the test :) )
09:08 <@mig5> and that's the other main thing i've been toying with (jenkins), although it's at an early stage in terms of aegir tests.
09:08 <@anarcat> cool :)
09:08 <@mig5> but i think we could use it more and more
09:08 <@anarcat> that is freakin awesome
09:08 <@anarcat> can you paste urls for that here?
09:08 <@anarcat> i'm really lazy, nevermind :)
09:09 <@mig5> sure http://jenkins.greenbeedigital.com.au:8080/job/aegir%20install/
09:09 <@mig5> i'd like to at least give you or other developers access to that properly, so you can run tests
09:09 <@mig5> at my expense :)
09:09 <@mig5> as i figure you might catch migressions, and do me a favour
09:09 <@mig5> :)
09:10 <@anarcat> haha
09:10 <@anarcat> well, in this case the regression was mine wasn't it ;)
09:10 <@mig5> no matter
09:10 <@mig5> one other thing:
09:10 <@mig5> i'm less worried than you re: drupal.org's issues in releasing hostmaster
09:10 <@mig5> i think it would be nice
09:10 <@mig5> but it's not a blocker in my opinion
09:10 <@anarcat> ok
09:10 <@mig5> as our design works around it already
09:11 <@anarcat> ... since we depend on git
09:11 <@mig5> yeah
09:11 <@anarcat> ok
09:11 <@anarcat> but the release.sh doesn't know that :p
09:11 <@mig5> ah, true :)
09:11 <@anarcat> so i almost released a broken rc3 here :)
09:11 <@mig5> don't worry, i broke rc2
09:11 <@mig5> but i ignored it :)
09:11 <@anarcat> eh
09:11 <@anarcat> ok
09:12 <@anarcat> so if you want to break^Wrelease rc3 tomorrow, or anytime, in fact, be my guest
09:12 <@mig5> don't want to make more work for us in the release.sh though. but, i'm afraid i'm still crippled with a 'don't wait for drupal.org to catch up with us' mentality :)
09:12 <@mig5> ok
09:12 <@anarcat> that's alright
09:13 <@anarcat> alright, anyone else?
09:13 <@mig5> i'll have some time, this time tomorrow
09:13 <@anarcat> omega8cc doesn't seem to be here, so i'll talk for her a little :)
09:13 <@anarcat> she found a vhost injection vulnerability in the alias
09:13 <@mig5> oh yeah
09:13 <@anarcat> it was fixed in head and I *think* i merged in stable
09:13 <@mig5> did the security team say anything?
09:13 <@anarcat> which is why i wanted to make a release
09:13 <@anarcat> yeah
09:13 <@anarcat> no embargo, just release
09:14 <@anarcat> since it's not a stable release, it's ok
09:14 <@mig5> ok
09:14 <@anarcat> so don't tag it as a security release either, because then it gets unpublished and all the shit
09:14 <@mig5> she has some nginx batch updates in the queue as well, since we never really test those ourselves, we should probably just roll them in
09:15 <@mig5> they missed rc2 already
09:15 <@mig5> http://drupal.org/project/issues?text=&projects=hosting%2C+provision%2C+...
09:15 <@anarcat> yup
09:15 <@anarcat> a good review of the needs review patches would be good, but not mandatory
09:15 <@anarcat> too bad we got that silly security issue otherwise that would have been 1.0 :P
09:15 <@mig5> oh well. i admit i didn't read the security vulnerability properly. how was it exploitable?
09:15 <@anarcat> darthsteven: please do submit a patch for that stuff, it seems like gold
09:15 <@mig5> i spose i could find the ticket
09:16 <@anarcat> oh and i think we should fix this too: http://drupal.org/node/1108810
09:16 <@anarcat> Files in sites/example.org/private are accessible.
09:16 <@mig5> yeah
09:16 <@anarcat> this is the security issue: http://drupal.org/node/1098304
09:16 <@anarcat> i thought the private files was already done
09:16 <@mig5> i thought we could stick it in the platform vhost
09:16 <@mig5> the deny all
09:16 <@mig5> his .htaccess is probably being ignored for that reason
09:17 <@mig5> in that we don't have AllowOverride
09:17 <@anarcat> yes, the .htaccess are ignored, on purpose
09:17 <@mig5> yep
09:17 <@anarcat> okay folks, i need to go!
09:17 <@mig5> so i thought we could inject that into the template ourselves
09:17 <@mig5> sound sane?
09:17 <@mig5> ok
09:17 <@anarcat> yep
09:17 <@mig5> have fun with your switch
09:17 <@mig5> cheers
09:17 <@anarcat> hehe i will :)
09:17 <@anarcat> ciao ciao

(06:02:27 PM) anarcat: mig5 / Vertice / darthsteven / EclipseGc / mvc / omega8cc / sfyn / skwashd / ergonlogic : scrum time!
(06:02:35 PM) EclipseGc: anarcat: yay
(06:02:43 PM) anarcat: joestewart: scrum!
(06:02:48 PM) darthsteven: crouch...touch...engage
(06:02:52 PM) anarcat: shrop / univate : scrum!
(06:02:57 PM) anarcat: alright
(06:03:31 PM) anarcat: so welcome everybody, sorry i'm little late :)
(06:03:35 PM) anarcat: i got tons of stuff :)
(06:03:39 PM) anarcat: first
(06:03:41 PM) anarcat: master is dead
(06:03:52 PM) anarcat: being an anarchist and all, no masters no god and everything ;)
(06:04:00 PM) anarcat: more seriously - we're all on 6.x-1.x now
(06:04:09 PM) anarcat: it was too much of a pain to sync that all the time
(06:04:20 PM) EclipseGc: heh
(06:04:32 PM) darthsteven: anarcat: has the master branch actually been removed now?
(06:04:40 PM) anarcat: darthsteven: yes, it's dead.
(06:04:49 PM) darthsteven: cool
(06:04:51 PM) anarcat: also, i have cleaned up the docs regarding the branch naming conventions here: http://community.aegirproject.org/node/187
(06:04:59 PM) ergonlogic: long live 6.x-1.x!
(06:05:05 PM) anarcat: reviews of that from the docs team would be welcome
(06:05:18 PM) anarcat: speaking of which, we talked about having maintainers for various sections of the project
(06:05:28 PM) anarcat: the first of which is the docs team, spearheaded by darthsteven and ergonlogic
(06:05:40 PM) anarcat: i don't remember the full list of teams, but i'll dig it out later
(06:05:55 PM) anarcat: so congrats to the docs team for the awesome work so far, more on that from darthsteven ltr i guess
(06:06:00 PM) anarcat: i did the roadmap for 2.0
(06:06:07 PM) anarcat: http://community.aegirproject.org/roadmap/2.0
(06:06:16 PM) anarcat: everyone is strongly encouraged to review and augment
(06:06:21 PM) anarcat: and especially take tasks
(06:06:48 PM) anarcat: koumbit will *not* do everything in there, but we *will* make a 2.0 release to deploy our changes in production, so the stuff that's not being taken care of will be pushed to 3.0
(06:07:12 PM) arianek is now known as arianekPHONE
(06:07:13 PM) anarcat: i would love to get betas for 2.0 released by the end of summer, with rcs in automn (ie. koumbit runnin 2.x in production by the end of the summer)
(06:07:21 PM) anarcat: we release rc3
(06:07:24 PM) anarcat: i want to release rc4
(06:07:26 PM) anarcat: tonight
(06:07:32 PM) EclipseGc: yay
(06:07:32 PM) anarcat: we have a bunch more changes
(06:07:47 PM) anarcat: especially the symlink stuff  (now sites are symlinked into /var/aegir/clients  for easier access)
(06:07:53 PM) anarcat: provisionacl has been updated to fix the perms there too
(06:08:08 PM) anarcat: debian packages have been released and uploaded to debian.koumbit.net
(06:08:11 PM) mig5: whoop, daylight savings screwed me. morning
(06:08:23 PM) EclipseGc: morning mig5
(06:08:26 PM) anarcat: morning mig5 ! :)
(06:08:47 PM) anarcat: there's been a few bugs with the debian packages, mostly with the new installs (because i'm mostly testing upgrades from our existing installs)
(06:08:56 PM) anarcat: upgrades work well, installs need testing but should work now
(06:09:11 PM) anarcat: the docs have been updated so that the manual install doesn't use install.sh
(06:09:16 PM) anarcat: which has been removed from the tree
(06:09:23 PM) anarcat: completely
(06:09:33 PM) anarcat: and the manual docs have been updated to use hostmaster-install instead
(06:09:40 PM) anarcat: and favor the debian automatic installs through packages
(06:10:01 PM) anarcat: koumbit will deploy the stable branch in staging tonight or tomorrow and rc4 in prod tomorrow
(06:10:06 PM) anarcat: that's about it for me i think
(06:10:17 PM) anarcat: oh and i'm in a retreat in the woods to code like crazy for a week or two
(06:10:31 PM) omega8cc: haha
(06:10:31 PM) anarcat: i'm trying to work on the d7 port, but if people want to join that effort, that would be welcome
(06:10:43 PM) anarcat: i'll also focus on bootstrap security, as i see fun
(06:10:49 PM) anarcat: prioritisation welcome
(06:10:53 PM) anarcat: ok, next!
(06:10:58 PM) mig5: i've done nothing, i'm sick and also have busted my back. also, i fly to europe end of next week, what great timing
(06:11:06 PM) mig5: so i don't expect you'll get much out of me until end of may now
(06:11:31 PM) mig5: that's it for my pep talk
(06:11:35 PM) anarcat: yay! ;)
(06:11:38 PM) omega8cc: mig5: welcome to eu!
(06:11:41 PM) anarcat: well, rest and get well :)
(06:11:45 PM) mig5: thanks
(06:11:57 PM) EclipseGc: I also have done nothing, but anarcat if you're doing a 7.x upgrade I would love to be available in any capacity that you might find useful. Be that review, or just as someone to bounce ideas at
(06:12:08 PM) anarcat: EclipseGc: gotcha
(06:12:19 PM) anarcat: so let's welcome our new dev here - darthsteven , do you have something to share?
(06:12:33 PM) darthsteven: sure
(06:13:02 PM) darthsteven: So, prompted by ergonlogic's issue, I asked for commit access to aegir to work on the documentation
(06:13:13 PM) mode (+o darthsteven) by anarcat
(06:13:14 PM) darthsteven: and it was granted
(06:13:23 PM) anarcat: great timing :)
(06:13:30 PM) EclipseGc: woot, now he can kick us all
(06:13:36 PM) darthsteven: hurrah!
(06:13:46 PM) darthsteven: (no idea how to though)
(06:13:49 PM) anarcat: congratulations! :)
(06:13:55 PM) darthsteven: so yeah, just been working on some docs
(06:13:57 PM) anarcat: darthsteven: /kick EclipseGc now now
(06:13:58 PM) anarcat: ;)
(06:13:59 PM) omega8cc: darthsteven: congrats!
(06:14:05 PM) EclipseGc: :-(
(06:14:10 PM) omega8cc: lol
(06:14:12 PM) darthsteven: and wrote an article about passing data from the Aegir frontend to the backend
(06:14:12 PM) anarcat: EclipseGc: just kidding :)
(06:14:15 PM) EclipseGc: heh
(06:14:23 PM) ***EclipseGc saw that
(06:14:32 PM) mode (+v shrop) by anarcat
(06:14:45 PM) EclipseGc: http://www.computerminds.co.uk/articles/storing-data-aegir
(06:14:58 PM) anarcat: darthsteven: that's nice!
(06:15:04 PM) anarcat: darthsteven: we should copy that into the manual somewhere...
(06:15:14 PM) darthsteven: from our work on the docs so far, I wonder if we wanted to clean up the API before the 1.0 final release?
(06:15:23 PM) darthsteven: it's not hugely consistent
(06:15:27 PM) EclipseGc: heh
(06:15:38 PM) mode (+v ergonlogic) by anarcat
(06:15:42 PM) darthsteven: but that would mean big changes I guess, so 2.0 stuff
(06:15:54 PM) ergonlogic: I've been promoted
(06:15:56 PM) anarcat: darthsteven: i would also think that api changes at this point would be a bit daring
(06:16:14 PM) anarcat: darthsteven: i would rather tag those inconsistencies as issues for 2.x
(06:16:17 PM) darthsteven: sure
(06:16:19 PM) anarcat: darthsteven: but document, document
(06:16:32 PM) anarcat: also, i think we should aim for a short 1.0 release cycle
(06:16:35 PM) darthsteven: so, plans are to add lots more documentation over the next days/weeks
(06:16:41 PM) anarcat: esp. because we're having api issues and so on
(06:16:42 PM) darthsteven: that's it for me
(06:16:46 PM) anarcat: alright
(06:16:57 PM) anarcat: thanks darthsteven and welcome again in the crew
(06:17:07 PM) anarcat: so a parenthesis on the statuses in this channel
(06:17:13 PM) anarcat: +o is for developers
(06:17:37 PM) anarcat: we're all equal there - if you need access to some resource on aegirproject.org or drupal.org, just ask and it will be granted
(06:17:47 PM) anarcat: +v is for (currently) occasional contributors
(06:17:53 PM) anarcat: it's the way to become a dev :)
(06:18:09 PM) anarcat: end of parenthesis
(06:18:19 PM) anarcat: so anyone else has something to add to our (late) scrum?
(06:18:19 PM) anarcat: omega8cc: ?
(06:18:53 PM) omega8cc: nothing from me this week, I'm sick, but hope to add something next week
(06:18:57 PM) anarcat: i can speak quickly for sfyn, who made his first official release of uc_hosting (1.0-beta1), ubercart integration
(06:19:06 PM) anarcat: which we're going to deploy soon
(06:19:18 PM) anarcat: also, we'll need to figure out where the heck univate has gone :)
(06:19:25 PM) anarcat: if anybody saw him, let me know ;)
(06:19:49 PM) ergonlogic: So, for my part, I've actually been pretty busy... 
(06:19:57 PM) ergonlogic: testing some of the aegir contrib modules
(06:20:09 PM) ergonlogic: some functional updates to the community site (spread out over the past few weeks really)... and more to come
(06:20:19 PM) ergonlogic: Some documentation, though I feel I need to better understand how to document hooks properly... 
(06:20:28 PM) ergonlogic: I'll be trying to debug some issues on api.aegirproject.org
(06:20:42 PM) ergonlogic: And I have a new Aegir contrib module (https://github.com/ergonlogic/hosting_saas) that denies uid1 to clients creating sites, and assignes them a role of our choosing
(06:20:52 PM) ergonlogic: which I'll release shortly on d.o, I think
(06:21:05 PM) ergonlogic: that's it, I think
(06:21:06 PM) anarcat: for hooks, we need to add sample code for it to make sense, e.g. hook_post_install()
(06:21:26 PM) darthsteven: ergonlogic: Feel free to ask me about documentation!
(06:21:30 PM) EclipseGc: ergonlogic: nice
(06:21:31 PM) anarcat: ah - ergonlogic and darthsteven - do we want to refactor your code straight into 1.0 core? or maybe we should wait for 2.x?
(06:21:33 PM) ergonlogic: I've some experience with a coule now, so I can try to put something together
(06:21:43 PM) ergonlogic: s/coule/could
(06:22:14 PM) darthsteven: anarcat: we're working in a branch of 1.0
anarcat AntiNSA-AFK 
(06:22:32 PM) anarcat: darthsteven: for docs, but i was talking about the scheduling, the dispatcher, and saas stuff
(06:22:46 PM) darthsteven: anarcat: ah okay
(06:22:48 PM) anarcat: darthsteven: i think we can merge that branch in rc4 - it's really all just docs
(06:23:10 PM) anarcat: i also think we can merge documentation into 1.x releases after 1.0
(06:23:23 PM) ergonlogic: I'd be happy for aegir core to appropriate hosting_saas
(06:23:34 PM) anarcat: so anyways, i think that's it for our scrum
(06:23:35 PM) ergonlogic: I think it might mean another promotion ;)
(06:23:44 PM) anarcat: hopefully we'll have rc4 ready tonight or tomorrow
(06:23:48 PM) EclipseGc: yay
(06:23:53 PM) anarcat: and 1.0 ready by next week or something
(06:23:54 PM) EclipseGc: mass migrate will come back :-D
(06:24:00 PM) anarcat: EclipseGc: yeah, i fixed it
(06:24:02 PM) darthsteven: cool
(06:24:04 PM) EclipseGc: anarcat: yeah I saw
(06:24:05 PM) ergonlogic: sounds good
(06:24:10 PM) EclipseGc: anarcat: thx for that :-D
(06:24:27 PM) anarcat: if someone wants to volunteer for the 1.x branch maintenance, i'd be happy to explain how that works and help with the work
(06:24:42 PM) ergonlogic: 
(06:24:45 PM) EclipseGc: lol
(06:24:48 PM) anarcat: ergonlogic: :P
(06:25:02 PM) anarcat: ergonlogic / darthsteven : i think i was too quick about the offer to merge the modules in core - let's do that merge in 2.x instead
(06:25:13 PM) darthsteven: anarcat: agreed
(06:25:29 PM) anarcat: okay, who wants the amazing and wonderful job of uploading the log in the site?
(06:25:31 PM) ergonlogic: k
(06:25:38 PM) ergonlogic: I'll do it
(06:25:47 PM) anarcat: great!
(06:26:04 PM) anarcat: thanks everyone for coming

23:02 darthsteven: mig5: ping
23:02 darthsteven: anarcat: ping
23:02 darthsteven: Scrum?
23:02 hefring: Every Tuesday at 22h00 UTC: 15h00 San Francisco, USA (PST), 18h00 Montreal, Canada (EDT), 23h00 London, UK (CET), 08h00 (Wednesday) Melbourne, Australia (EST)
23:03 darthsteven: Guess this is going to be a quiet scrum then...
23:03 darthsteven: Well, I'll start
23:04 obicke: go for it
23:04 darthsteven: I've not done a whole lot of extra documentation, just all the constants in hostmaster, and a couple more hooks
23:04 darthsteven: I've been chasing ergonlogic about the api.a.o site not updating, he should be looking at it soon
23:05 darthsteven: hoping to still push some more docs before the 1.0 final release
23:05 darthsteven: that's it from me
23:05 darthsteven: anyone else?
23:06 darthsteven: EclipseGc, ergonlogic, grugnog, mvc, omega8cc, sfyn, shrop, skwashd or anyone else have anything to add?
23:06 obicke: • obicke is trying to round up anarcat and ergonlogic
23:07 EclipseGc: • EclipseGc was not reading
23:07 EclipseGc: • EclipseGc has nothing to add
23:08 shrop: Nothing at this point
23:08 shrop: When is v1 coming out?
23:09 darthsteven: soon
23:10 EclipseGc: • EclipseGc would like to point out his new power-module though http://drupal.org/project/path_profiler
23:11 darthsteven: I'll give this scrum until 22:15UTC
23:14 sethvincent: darthsteven: where are the api docs located?
23:15 darthsteven: sethvincent: api.aegirproject.org
23:15 sethvincent: thanks
23:16 darthsteven: that's the end of the scrum then

[22:00:51]  <@anarcat>  alright, welcome everybody to our weekly scrum
[22:01:04]  <@anarcat>  i'm your host for this week and we have a wonderful agenda :)
[22:01:09]  <@anarcat>  enough with the bull
[22:01:14]  <@anarcat>  1.0 IS RELEASED!!!!!
[22:01:17]  <@anarcat>  YEEHAAA! :)
[22:01:24]  <@mvc>  :)
[22:01:26]  <@darthsteven>  YEAH!!!
[22:01:26]  <@anarcat>  *AND* we have found our first RC bug!
[22:01:33]  <@anarcat>  http://drupal.org/node/1132514
[22:01:38]  <@anarcat>  d5 migrations are fucked! :)
[22:01:42]  <@anarcat>  so that's already fixed and great
[22:01:48]  <@anarcat>  and i am thinking of making 1.1 already
[22:02:06]  <@anarcat>  also, we found a low-hanging fruit here to make exportable backups easy: http://drupal.org/node/1047992
[22:02:17]  <@anarcat>  and i merged this in by mistake in 1.x, but now i think i won't revert it
[22:02:36]  <@anarcat>  http://drupalcode.org/project/provision.git/patch/1edd757f95b3f86a84ba72...
[22:02:43]  <@anarcat>  if anyone opposes, feel free to revert
[22:03:03]  <@anarcat>  it's not an API change, and it's a nice quick fix to have people with SFTP access able to download backups of their sites
[22:03:09]  <@anarcat>  so i think it would be nice to get this in
[22:03:18]  <@anarcat>  koumbit is now running 1.0 in production
[22:03:35]  <@anarcat>  and we're going to test head 1.x tomorrow, and if that works well we'll release 1.1
[22:03:46]  <@anarcat>  what else, what else
[22:04:04]  <@anarcat>  did i mention we have a candidate student for the summer of code?
[22:04:16]  <@anarcat>  http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/sdv_3...
[22:04:19]  <@anarcat>  here, i mentionned it
[22:04:24]  * mapleleaf has quit (Quit: ChatZilla 0.9.86.1 [Firefox 3.6.16/20110319135224])
[22:04:24]  <@anarcat>  results should be announced somewhere next week
[22:04:33]  <@anarcat>  his focus would be on the d7 port and maybe dns
[22:04:40]  <@anarcat>  so i decided to hold off on those tasks for now
[22:04:54]  * Chipie has quit (Quit: Leaving.)
[22:04:55]  <@anarcat>  i will however look more at inter site security
[22:04:57]  <@darthsteven>  all very cool
[22:05:02]  * FatGuyLaughing has quit (Quit: FatGuyLaughing)
[22:05:09]  <@anarcat>  and queueing, and i'd like to talk with darthsteven about that, but prolly more next week
[22:05:16]  <@anarcat>  so that's about it for me
[22:05:49]  <@anarcat>  mig5 darthsteven ergonlogic mvc omega8cc sfyn shrop skwashd - something to add to our weekly scrum?
[22:05:55]  <@darthsteven>  yup
[22:06:20]  <@anarcat>  oh, and of course, i forgot: http://community.aegirproject.org/discuss/2x-branch-created 2.x is opened for dev, and i merged the chained cert support there
[22:06:33]  <@darthsteven>  I've just come from a Drupal Meetup where I saw that drupal 5 migration bug demoed
[22:06:42]  <@darthsteven>  and now I know what caused it
[22:06:44]  <@darthsteven>  :)
[22:06:58]  <@anarcat>  and now you can tell them it's fixed already :)_
[22:07:17]  <@darthsteven>  So I took a look at at patch to add SSL chained certificates to provision
[22:07:32]  <@darthsteven>  It needed a bit of cleanup, but was okay
[22:07:43]  <@anarcat>  i agree, and merged it into 2.x
[22:08:06]  <@darthsteven>  I think I added some docs since the last scrum, and ergonlogic got the api.c.o site working
[22:08:36]  <@darthsteven>  ermm...that's it for me, nothing else Aegir related really
[22:08:45]  <@darthsteven>  hoping to write more docs though...
[22:08:51]  <@darthsteven>  done
[22:08:55]  <@darthsteven>  anyone else?
[22:09:09]  <@anarcat>  cool
[22:09:22]  <@anarcat>  omega8cc: ?
[22:09:35]  <@anarcat>  omega8cc: you mentionned something about tracking 2.x, can you expand on that?
[22:09:36]  <@omega8cc> I released Barracuda/Octopus 1.0-boa-T-8 with Aegir 1.0
[22:10:08]  <@omega8cc> anarcat: just switched to 2.x to continue with patches related to Nginx
[22:10:22]  <@anarcat>  i am, in general, a bit worried that we won't get as much testing on 2.x than we have on 1.x now that 1.x is declared stable, but i'll try to run 2.x on my home server - we were also thinking of running 2.x on a dev server at koumbit, but that has yet to happen
[22:10:26]  <@anarcat>  omega8cc: cool, nice to hear
[22:11:04]  <@omega8cc> anarcat: I will use 2.x in Barracuda head, so people will test it and I hope to get more feedback
[22:11:08]  <@anarcat>  cool
[22:11:31]  <@anarcat>  i was thinking of reworking the platform access control for april, we set that as a target, so maybe that will land in 2.x and maybe get merged in 1.x if it doesn't break any apis
[22:11:41]  <@omega8cc> interesting that 5.x to 6.x to 7.x migrations worked for me
[22:11:48]  <@anarcat>  i am still looking for ways to radically change 2.x so that it's really different from 1.x :P
[22:12:01]  <@omega8cc> but I tested it only on basic core installs
[22:12:07]  <@anarcat>  i see
[22:12:12]  <@anarcat>  nice to hear anyways :)
[22:12:13]  <@ryanarmstrong>    anarcat: cross-site stats :P
[22:12:21]  <@ryanarmstrong>    *goes back into the background*
[22:13:25]  <@anarcat>  oh, darthsteven - this could use some more eyes as it touches on the context/services stuff that you may be familiar with: http://drupal.org/node/1074966
[22:13:41]  <@anarcat>  omega8cc: thanks for your feedback
[22:13:44]  <@anarcat>  anyone else?
[22:13:54]  <@anarcat>  ryanarmstrong: you'll have to expand on that after the scrum :)
[22:14:03]  <@ryanarmstrong>    will do, didn't want to derail :)
[22:14:07]  <@omega8cc> we need UI improved in 2.x, I will submit patches soon, and will propose Fetaures integration etc
[22:14:17]  <@anarcat>  omega8cc: great idea!
[22:14:31]  <@anarcat>  omega8cc: one idea about features was to drop our idea of "features" in favor of features.module
[22:14:38]  <@darthsteven>  anarcat: yeah I saw that, and it is on my radar, but I've not used any of the DNS stuff, but could look at the code anyways
[22:14:57]  <@omega8cc> right, and move install profile to profiler
[22:15:06]  <@omega8cc> maybe
[22:15:10]  <@anarcat>  omega8cc: yeah
[22:15:20]  <@anarcat>  omega8cc: ergonlogic was saying it was a good upgrade path to d7
[22:15:33]  <@anarcat>  alright
[22:15:35]  <@omega8cc> anarcat: yes, noticed that
[22:15:47]  <@anarcat>  we're pretty much done here, thanks for attending our scrum session and see you next week!
[22:16:02]  <@darthsteven>  I'm not sure that converting to features features would get us much, as we don't use CCK/fields
[22:16:07]  <@anarcat>  anyone wants to upload this log to the com site?
[22:16:26]  <@darthsteven>  will do
[22:16:28]  <@anarcat>  darthsteven: indeed..
[22:16:31]  <@anarcat>  darthsteven: cool! tx
[22:16:59]  <@anarcat>  darthsteven: as for the dns issue, it's not as much for the DNS but for the part where he changes the way config information is stored in the services objects
[22:17:03]  <@anarcat>  hairy stuff
[22:17:09]  <@anarcat>  alright, scrum end!

21:59 <@anarcat> hey
21:59 <@anarcat> gooood morning vietnam!
22:00 <@mig5> HELO
22:00 <@anarcat> alright
22:00  * anarcat SCRUM TIME!
22:00 <@anarcat> gosh this is early
22:00 <@anarcat> so welcome everyone
22:00 <@darthsteven> heh
22:01 <@anarcat> i'm your sleepy host, unless another timezone feels less jetlagged :)
22:01 <@mig5> getting sleepy :)
22:01 <@darthsteven> I'm your less sleepy host then
22:01 <@anarcat> yay! :)
22:01 <@darthsteven> Welcome to the scrum for 21 Jun 2011
22:01 <@darthsteven> Who wants to speak first?
22:01 <@darthsteven> anarcat?
22:01 <@anarcat> i can try! :)
22:02 <@anarcat> so i haven't published 1.2, but this time i have a good excuse
22:02 <@anarcat> we're really almost there - i want to test the debian packages first
22:02 <@anarcat> i was able to make an autobuilder in jenkins
22:02 <@anarcat> so jenkins now has a pgp key and can build packages. both from the debian branch and from the 1.x branch
22:02 <@anarcat> https://drupal.org/node/1183926
22:02 <@darthsteven> cool
22:03 <@anarcat> there are a good few questions in there that i'd like feedback about
22:03 <@anarcat> esp. from mig5
22:03 <@mig5> awesome, you are now our CI ninja :)
22:03 <@anarcat> crap :)
22:03 <@darthsteven> anything else anarcat?
22:03 <@anarcat> well, there's this daemon thing :)
22:04 <@anarcat> i played with darthsteven's queue runner, and it's awesom
22:04 <@anarcat> we're running it in production, working very well, got people impressed
22:04 <@anarcat> i want to merge it in 2.x
22:04 <@anarcat> and port our dispatcher to the d7 queue system
22:04 <@anarcat> i think we should make queue-runner 1.1
22:04 <@anarcat> i think that's about it for me!
22:05 <@darthsteven> mig5?
22:05 <@darthsteven> (thanks anarcat)
22:05 <@anarcat> welcome!
22:05 <@mig5> nothing from me this week, i need to catch up on the jenkins changes
22:05 <@darthsteven> okay, cool
22:05 <@darthsteven> I'll go next...
22:06 <@darthsteven> I looked at the daemon for running tasks with anarcat
22:06 <@darthsteven> resulting in a 1.1 release, which anarcat hasn't noticed :)
22:06 <@anarcat> haha cool
22:06 <@darthsteven> We also got the api site sorted last week, though mostly not down to me
22:06 <@darthsteven> which is ace!
22:07 <@mig5> nice
22:07 <@darthsteven> I added a new hook to enable friendly names for servers in lists of servers
22:07 <@darthsteven> and released a module that uses the hook
22:07 <@darthsteven> http://drupal.org/project/hosting_server_titles
22:08 <@darthsteven> I think I added a ton of documentation the week before too
22:08 <@darthsteven> which was nice
22:08 < chouchou> Hello,
22:08 <@anarcat> cool
22:08 <@darthsteven> but that's it from me
22:08 < chouchou> pls i have an issue,
22:08 <@anarcat> note that i documented the 2.x api changes here http://community.aegirproject.org/upgrading/path
22:08 < chouchou> first, i wouuld like to know how do I change the drush gid download source ?
22:08 <@darthsteven> chouchou: We're in the middle of a scrum, please hold for the end, then you can ask
22:08 <@anarcat> i think we should keep that page in mind when we change the API
22:08 <@darthsteven> anyone else have anything for the scrum?
22:09 <+omega8cc> I finally started publishing some nginx related docs on www.omega8.cc and will extract from there to re-post on c.a.o handbook, also some new nginx patches are in testing and should be sumitted for review shortly, we are sponsoring also Aegir session at http://drupaldesigncamp.net next week!
22:09 <@darthsteven> awesome
22:09 <@mig5> props to shrop who has done great work on the community site sorting some stuff out
22:09 <@darthsteven> omega8cc: anything else?
22:09 <@anarcat> all good
22:09 <+omega8cc> that is it from me, i think
22:10 <@anarcat> ah, note that i'll be at the drush test sprint next week, so i will probably miss the scrum
22:10 <@anarcat> if you guys have specifics of things i should work on with drush, let me know!
22:11 <@darthsteven> anyone else have anything to add?
22:11 <@darthsteven> I'll give it a minute...
22:11 <@anarcat> well, i'd like to chat quickly with mig5 about the jenkins stuff
22:11 <@anarcat> mig5: did you read up on the issue?
22:11 <@mig5> this one? https://drupal.org/node/1183926
22:12 <@anarcat> mig5: upy
22:12 <@anarcat> yup*
22:12 <@anarcat> basically, we need to decide this:
22:12 <@anarcat> 1. do we install/remove/update/whatnot on the jenkins server? (be scared)
22:12 <@anarcat> 2. do we install using dpkg -i or do we upload to debian.koumbit.net's unstable repository and use apt-get? (the latter has the disadvantage of having 
                 to wait a undetermined delay for repo to catchup, but has the upside of broadening the test capabilities)
22:12 <@anarcat> i am thinking more and more of this as a build bot, with packges uploaded to debian.koumbit.net/unstable
22:13 <@anarcat> and then everyone can test them, including jenkins or "the cloud", from jenkins
22:13 <@mig5> 1. is fine with me but i was already scared :) but as far as I can tell, it's the only way to sanely chain tasks.. (as opposed to an isolated 
              cloud-generated VPS)
22:14 <@mig5> the fundamental thing i want to do with theses tests, is pretend like we are a user
22:14 <@anarcat> well that's the thing, if we upload to debian.k.n, then we can run install/upgrade/whatever independently...
22:14 <@mig5> except with preseeding :)
22:14 <@mig5> so i think the apt-get is good
22:14 -!- bgm_ is now known as bgm
22:14 <@anarcat> ok
22:14 <@anarcat> mig5: do you know about jenkins's "tasks"?
22:14 -!- bgm [~bgm@2607:f748:1200:105::5] has quit [Changing host]
22:14 -!- bgm [~bgm@pdpc/supporter/active/bgm] has joined #aegir
22:14 <@mig5> no
22:14 <@anarcat> ok
22:14 <@mig5> i've only done build steps
22:15 <@anarcat> i tried to play with that, but i don't feel it's what we need, basically...
22:15 <@anarcat> it's a weird thing
22:15 <@anarcat> so okay, that's cool
22:15 -!- mode/#aegir [+v shrop] by ChanServ
22:15 <@anarcat> i think i'll try to setup fabric stuff to deploy debian packages remotely
22:15 <@anarcat> and of course upload to debian.k.n
22:15 <@mig5> deploy as in send to koumbit.d.n ?
22:15 <@mig5> er
22:15 <@mig5> ah
22:15 <@anarcat> and fix the preseed
22:16 <@mig5> so by deploy debian packages remotely you mean, build on fresh VPS?
22:16 <@mig5> as i am not against the former
22:16 <@anarcat> deploy as in ssh cloud.vps.foo 'apt-get install aegir; drush provision-tests ; apt-get remove aegir'
22:16 <@mig5> so long as we can clean up our mess on the jenkins server
22:17 <@anarcat> well, i'm worried about not being able to do that
22:17 < chouchou> are you free now?
22:17 <@mig5> my main worry about cloud.vps.foo is we may lose the ability to chain builds
22:17 <@anarcat> *and* about interop problems with jenkins itself
22:17 <@darthsteven> Anyone else have anything for the scrum? Otherwise we'll wrap it up there, and leave mig5 and anarcat to it...
22:17 <@anarcat> darthsteven: yup, ok
22:17 <@darthsteven> 

[22:01:04]    <mig5>    scrum time
[22:01:12]   <omega8cc>    hello!
[22:01:12]   <mig5>    anarcat sends his apologies for this week
[22:01:25]    <mig5>    but I hear he had a good time at the drush sprint and got some good work done, so hopefully we'll hear more about that soon
[22:02:03] <mig5>    me, i once again didn't do anything.. oh, I did add to the jenkins deb install of aegir to uninstall and purge the packages before destroying
[22:02:13]   <mig5>    which is a final good test of those packages
[22:02:18] <halcyonCorsair>  omega8cc: i'm trying a barracuda/octopus upgrade before i try again
[22:02:40] <mig5>    i think we are well overdue for a 1.2 release, I am conscious there are a lot of patches from omega8cc for review (I think?) so we should get those in
[22:02:53]   <halcyonCorsair>  omega8cc: but i was having trouble replicating the site installation commands, i think there might have been some arguments i was missing?
[22:02:55]   <omega8cc>    halcyonCorsair: please wait 15 minutes, we have scrum time
[22:02:56]   <mig5>    that's it from me, over to darthsteven and omega8cc
[22:03:27] <darthsteven> sure
[22:03:52] * Harley has joined #aegir
[22:03:56]   <darthsteven> I got the Jenkins deb install of aegir working
[22:04:07]   <mig5>    epic
[22:04:13] <darthsteven> and worked on getting notification integration with Aegir
[22:04:26]    <darthsteven> http://drupal.org/project/hosting_notifications
[22:04:42]  <mig5>    oh nice. i saw somewhere a sandbox link but it had disappeared
[22:04:47]   <darthsteven> So I now get push notifications on my iPhone when Aegir tasks fail
[22:04:51]   <darthsteven> which is nice
[22:04:58]    <darthsteven> write-up coming soon
[22:05:02] <mig5>    nice. Notifo?
[22:05:11]    <darthsteven> that's it from me
[22:05:25]   <darthsteven> (using prowl, but whatever messaging module supports is possible)
[22:05:36]    <mig5>    gotcha
[22:06:23]   <mig5>    omega8cc, anything to add? other than 'commit my patches you bastards' :)
[22:06:42]  <omega8cc>    ok, so I want to attack that weird critical today: http://drupal.org/node/1196034 and it lock all our upgrades schedule currently, and then will submit next round of improvements to the Nginx config plus - yay! Aegir UI patches!
[22:06:42] <hefring> http://drupal.org/node/1196034 => Paths to images are broken in D7 after site clone/rename => Provision, Code, critical, needs work, 3 comments, 3 IRC mentions
[22:07:52]    <mig5>    cool!
[22:07:55]    <omega8cc>    and that is it from me, but the UI changes are long overdue and I want to share them finally
[22:09:09] <mig5>    omega8cc: i wonder if that patch of yours needs to be applied to the deploy_7.inc file?
[22:09:13]  <mig5>    as opposed to deploy.inc
[22:09:18] <mig5>    but i've forgotten how it all works
[22:09:54] <mig5>    don't think it would change that result anyway
[22:09:57]  <omega8cc>    mig5: that is exactly what I think, it misses d7 specific stuff there completely
[22:10:04] <mig5>    strange
[22:10:08]  <omega8cc>    yeah
[22:10:15] <mig5>    anyway - anyone else got something to add to the scrum? ergonlogic?
[22:10:25]  <joestewart>  not directly on aegir but I posted two patches to drush_make that are useful for aegir. one that adds ability to set options in the makefile - http://drupal.org/node/1206340 the other updated a patch that allows setting working-copy per project - http://drupal.org/node/958844
[22:10:25] <hefring> http://drupal.org/node/1206340 => introduce an options array in the root level of the makefile => Drush Make, Code, normal, needs review, 0 comments, 1 IRC mention
[22:10:26]    <hefring> http://drupal.org/node/958844 => PATCH: Allow [working-copy] in makefile as well as on commandline => Drush Make, Code, normal, needs review, 18 comments, 1 IRC mention
[22:10:42]   <mig5>    nice, I saw the working-copy patch update
[22:11:08]    <mig5>    also see Owen's Drush sprint overview here for those interested: http://civicactions.com/blog/2011/jun/30/drush_code_sprint_report
[22:11:29]  * CraHan is now known as CraHan_out
[22:11:52]  <mig5>    ok, scrum done I think, and i'll do the log
[22:11:56] <mig5>    thanks all
[22:12:04]   <omega8cc>    thanks!

(08:01:34 AM) anarcat: heey scrum time
(08:01:39 AM) anarcat: mig5 / darthsteven : scrum!
(08:01:45 AM) anarcat: omega8cc / sfyn / shrop : scrum time
(08:01:52 AM) anarcat: am i the only one awake? :)
(08:01:59 AM) omega8cc: hello!
(08:02:01 AM) ergonlogic: anarcat: not the *only* one
(08:02:14 AM) ergonlogic: hi all
(08:02:35 AM) anarcat: hello ergonlogic !
(08:02:50 AM) anarcat: so welcome to our weekly scrum
(08:02:52 AM) anarcat: i don't have much to say
(08:02:57 AM) anarcat: i've been away for a while
(08:03:03 AM) anarcat: vacations, drush sprint, etc
(08:03:12 AM) anarcat: i'll try to do a reportback of that great drush sprint soon
(08:03:36 AM) anarcat: but basically, i worked on jenkins, debian packaging and cleaning up the drush bootstrap process to make real unit tests possible
(08:03:49 AM) anarcat: so we can now test *functions* (instead of just commands) in the drush unit test framework
(08:03:53 AM) anarcat: which will be useful for provision
(08:03:54 AM) anarcat: now
(08:04:01 AM) anarcat: how's 1.x doing?
(08:04:14 AM) anarcat: i have on my tuesday todo (and had for a while) to release 1.2
(08:04:27 AM) anarcat: so i'm thinking to test the 1.x debian packages all over the place then just release the damn thing
(08:04:53 AM) anarcat: how does that sound?
(08:04:55 AM) omega8cc: anarcat: there are patches waiting in the queue
(08:05:02 AM) anarcat: ah darn :)
(08:05:05 AM) anarcat: omega8cc: your patches? :)
(08:05:07 AM) omega8cc: ;)
(08:05:10 AM) omega8cc: yep
(08:05:13 AM) anarcat: hehe ok
(08:05:17 AM) anarcat: that shouldn't be a big issue
(08:05:26 AM) omega8cc: simple stuff
(08:05:59 AM) anarcat: ok, so i'll merge that in before release
(08:06:09 AM) omega8cc: thanks
(08:06:09 AM) anarcat: so one last thing for me
(08:06:17 AM) anarcat: i'll be going on a looong holiday around drupalcon
(08:06:33 AM) anarcat: i'm leaving on august 3rd for europe, then going to drupalcon, then i'm gone for september
(08:06:54 AM) anarcat: so that could stall dev of 2.x for a little longer, but i'll be back in full force after that
(08:07:22 AM) anarcat: ah and before i forget: darthsteven: our hosting-queue-runner daemon disappeared here for the first time ever, not sure why, i'll try to track it down today
(08:07:29 AM) anarcat: okay, anyone else has something to add here?
(08:07:45 AM) ergonlogic: For my part, I posted an Aegir extension module on d.o: Hosting Profile Roles
(08:07:50 AM) ergonlogic: ... and I've begun hacking on a couple more
(08:07:55 AM) ergonlogic: And worked on a couple small patches to Drush
(08:08:09 AM) ergonlogic: I've been testing .deb installs on some client VPSs, which has been going smoothly
(08:08:12 AM) omega8cc: not much from me this week, besides fixed support for open public and vudeola
(08:08:33 AM) omega8cc: err, videola
(08:08:52 AM) ergonlogic: ooh, lullabot's published it now?
(08:08:56 AM) omega8cc: yep
(08:09:04 AM) ergonlogic: I'll have to check it out
(08:09:14 AM) omega8cc: and merged my fix already
(08:09:44 AM) Aciid: oh no, videola. I hope it doesn't catch on at the company that we should start offerin sites with it..
(08:09:56 AM) Aciid: videola's performance and seek capabilities are horrible
(08:10:08 AM) Aciid: or maybe it's lullabot's CDN
(08:11:28 AM) anarcat: alright, anyone else?
(08:11:43 AM) ***anarcat notices our gsoc student missing
(08:11:52 AM) anarcat: has he checked in at all while i was gone?
(08:12:13 AM) omega8cc: I didn't notice
(08:12:26 AM) anarcat: that's reallly too bad
(08:12:32 AM) anarcat: i'll have to do an evaluation soon
(08:12:57 AM) ergonlogic: oh, one other things (not to do with our GSoC student), Koumbit is now accepting donations in support of the Aegir Project
(08:13:15 AM) ergonlogic: there's a link on the front page of community.aegirproject.org
(08:14:29 AM) ergonlogic: if/when we receive any donations, we'll have to figure out how to disburse them
(08:14:33 AM) anarcat: ergonlogic: yeah, mig5 wanted to talk about this, actually
(08:14:55 AM) anarcat: ergonlogic: he was suggesting we (koumbit) get a rackspace cloud account and deal with the donations
(08:14:59 AM) anarcat: where are the donations going now?
(08:15:16 AM) ergonlogic: anarcat: Koumbit's PayPal acct
(08:15:23 AM) anarcat: ok, good
(08:15:46 AM) anarcat: alright
(08:15:57 AM) anarcat: so if there's nobody else, that will be it for our weekly scrum!
(08:16:13 AM) ergonlogic: I'll post to the community site
(08:16:28 AM) omega8cc: thanks

22:00 <@anarcat> alright
22:00 <@anarcat> scrum time!
22:00 <+omega8cc> oh
22:01 <@mig5> I didn't know if it had moved time yet or what :)
22:01 <@anarcat> darthsteven: scrum!
22:01 -!- Irssi: #aegir: Total of 75 nicks [4 ops, 0 halfops, 4 voices, 67 normal]
22:01 <@anarcat> so hi
22:01 <@anarcat> i am not sure what to do about the time
22:01 <@anarcat> steven says he can't attend every week because it's too late
22:02 <@anarcat> mig5: and you seem also to have issue about i
22:02 <@mig5> not ideal for everyone, ever.. maybe we just tolerate a 'rotation' of devs who might not always be here
22:02 <@anarcat> t
22:02 <@mig5> maybe it helps that I never have anything to add... :/
22:02 <@anarcat> well
22:02 <@anarcat> i will be on a holiday for two months
22:02 <@anarcat> so maybe we can flip that around somehow
22:03 <@anarcat> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2011&mont... É
22:03 <@anarcat> ?
22:03 <@anarcat> 8hAM london, 5PM melbourne, midnight LA
22:04 <@mig5> we'll see if darthsteven complains about the early start :)
22:04 <@mig5> fine with me
22:04 <@darthsteven> Fine with me
22:04 <@anarcat> 2 am EDT
22:04 <@anarcat> anyways
22:04 <@anarcat> i don't know what to do
22:04 <@anarcat> and i wish somebody else would figure it out basically :P
22:05 <+omega8cc> fine with me too ^^
22:05 <@mig5> it won't ever work until I quit :)
22:05 <@darthsteven> Could we rotate early and late on alternate weeks?
22:05 <@anarcat> we could!
22:05 <@anarcat> and really, we need to keep in mind we don't absolutely need to readjust for seth
22:05 <@anarcat> he was pretty clear about that
22:06 <@darthsteven> So long as it's not too confusing
22:06 <@anarcat> he can (and should) provide feedback in other ways
22:06 <@anarcat> the 8AM is kinda hard on some people here though
22:06 <@anarcat> so anyways
22:07 -!- Chipie [~Chipie@mue-88-130-106-140.dsl.tropolys.de] has quit [Quit: Leaving.]
22:07 <@anarcat> to be clear - i would rather see both of you guys (mig5 and darthsteven) than bring seth back in the loop and loose you :P
22:07 <@anarcat> so i suggest we stick to the schedule at least until i leave for europe
22:07 <@mig5> don't worry too much
22:07 <@anarcat> then you guys can organize as you want
22:07 <@mig5> sure
22:07 <@anarcat> which brings me to
22:08 <@anarcat> somebody should probably take over gsoc mentorship while i'm gone
22:08 <@anarcat> i may have *some* time to followup, but really not a lot
22:08 <@anarcat> i'll be traveling all over the place and I won't be able to prod seth
22:08 <@anarcat> and he needs prodding :P
22:08 <@anarcat> so if somebody could take that over, that would be cool
22:09 -!- redShadow[2V] [~redShadow@93-62-151-43.ip23.fastwebnet.it] has joined #aegir
22:09 <@anarcat> it's just sending an email from time to time to say "hey what's up" - he's usually pretty responsive
22:09 <@anarcat> i tried to encourage him to document hist stuff on the commmunity site
22:09 <@mig5> ok. I am probably doing the least all round so I will step up
22:09 <@anarcat> and we reoriented his roadmap
22:09 <@anarcat> which he needs to document
22:09 <@anarcat> mig5: awesome!
22:09 <@mig5> if you could brief me in an email on the current status, maybe cc him
22:09 <@anarcat> mig5: i can forward you the relevant communications
22:09 <@mig5> so i'm up to date
22:09 <@mig5> snap
22:09 <@anarcat> hehe
22:09 <@anarcat> cool
22:09 <@anarcat> so that will be it
22:10 <@anarcat> i will probably receive the "hey you need to evaluate this guy" at the end of the program, but we'll cross that bridge when we get there
22:10 <@anarcat> alright
22:10 <@anarcat> now
22:10 <@anarcat> i released 1.2
22:10 <@anarcat> whooohooo!
22:10 <@anarcat> http://community.aegirproject.org/1.2
22:10 -!- romaingar [5d197493@gateway/web/freenode/ip.93.25.116.147] has joined #aegir
22:10 <@mig5> thanks for that anarcat, it got a good response
22:10 <@anarcat> omega8cc found what seems to be a critical with the new cron code: https://drupal.org/node/1222208
22:11 <@anarcat> i tried to roll out a patch for it and it failed to work, and i'm totally puzzled as to why
22:11 <@darthsteven> Cool
22:11 <@anarcat> i don't see the same issue at all here
22:11 <@mig5> i wondered if it was nginx specific, caching HTTP results
22:11 <@anarcat> and i'm about to give up on it for now, as we don't see the bug at koumbit
22:11 <@anarcat> mig5: s/was/is/
22:11 <@anarcat> the issue is still there
22:11 <@mig5> yeah.
22:11 <@anarcat> so i don't get it
22:11 <@anarcat> the original code *was* broken, but with the patch it should be fine
22:12 <@anarcat> http://drupalcode.org/project/hostmaster.git/commitdiff/f46c7ce
22:12 <@mig5> it would not be the first time i've seen nginx cache a 404
22:12 <+omega8cc> there is no caching there
22:12 <+omega8cc> none
22:12 <@mig5> 2 days is too much though
22:12 <@mig5> ok
22:12 <@darthsteven> Not sure I have time, but will try to look if I can
22:12 <+omega8cc> just one 403 error locks the queue
22:13 <@anarcat> omega8cc: and you did try the patch?
22:13 <@anarcat> omega8cc: do you see this watchdog entry?         watchdog('hosting_cron', 'cron failed on site %site with error %error', array('%site' => $site->title, '%error' => $response->error), WATCHDOG_NOTICE);
22:13 <+omega8cc> yes, and reported failure there
22:13 <@anarcat> we'll need more juice to figure that one out
22:13 <+omega8cc> yes, it says 403, as before, for site taken offline for maintenance
22:14 <+omega8cc> this should be easy to reproduce
22:14 <@anarcat> ok
22:14 <@anarcat> so anyways, maybe darthsteven will look into it
22:14 <@anarcat> we can talk more about it after the scrum
22:14 <@anarcat> i monopolized the space too long :)
22:14 <@anarcat> otherwise yeah, release++
22:14 <@anarcat> the debian packages kick major asses
22:15 <@anarcat> and we're deploying a bunch of vservers with those
22:15 <@anarcat> so it's fun
22:15 <@anarcat> that's about it for me, anyone else?
22:15 <@mig5> nothing here
22:16 <@anarcat> darthsteven?
22:16 <@anarcat> oh crap, that should be a continue, not a break
22:16 <@anarcat> i'm on acid
22:16 <@anarcat> ffs
22:17 <@mig5> ??
22:17 <@mig5> ah
22:17 <@anarcat> anyways, i have a fix for the cron thing
22:17 <@mig5> haha
22:17 <@darthsteven> I've been on holiday, and not had time to do anything Aegir related
22:17 <@darthsteven> Will do something Aegir related in the next week for sure
22:17 <@darthsteven> Need to check up on our Drupalcon presentation with anarcat
22:18 <@anarcat> darthsteven: any specific time you want to do this?
22:18 <+omega8cc> hah, break does just that - breaks things! lol
22:18 <@darthsteven> anarcat: not fussy about a time
22:18 <@mig5> failed to fail failed :)
22:19 <@darthsteven> anarcat: soon though, as I think they need things from us?
22:20 <@anarcat> yeah, i've been kind of sloppy with this
22:20 <@anarcat> darthsteven: maybe we can talk later today?
22:21 <@anarcat> omega8cc: try cb0c2d2

22:21 <@darthsteven> sure, I'm around for the next 3 hours or so...
22:21 -!- scientist [~scientist@206.248.137.227] has joined #aegir
22:21 <@anarcat> ok
22:21 <+omega8cc> anarcat: sure, thanks
22:21 <@anarcat> i think that's it for our scrum unless somebody else wants to kick in...
22:21 <@anarcat> who's it?
22:22 <@anarcat> (who wants to upload the scrum log, that is)
22:22 <@mig5> i'll do it
22:22 <@darthsteven> I can
22:22 <@darthsteven> oh
22:22 <+omega8cc> :)
22:22 <@darthsteven> go for it mig5

[12:00pm] anarcat scrum time!
[12:00pm] anarcat: hello people
[12:00pm] univate: hello
[12:00pm] anarcat: welcome to our morning weekly scrum
[12:00pm] omega8cc: hi
[12:00pm] anarcat: hey univate what's up
[12:00pm] anarcat: alright
[12:00pm] You left the chat by being disconnected from the server.
[12:01pm] You rejoined the room.
[12:01pm] You were granted voice by ChanServ.
[12:01pm] anarcat: univate: i don't know! 
[12:01pm] anarcat: so our gsoc student is supposed to take care of that, but i didn't get any news from him since the evaluation
[12:02pm] anarcat: which is really too bad
[12:02pm] anarcat: i'll try to ping him by email now
[12:02pm] mig5: anarcat: please send me an email before you go, re GSOC student
[12:02pm] mig5: or cc me on that one ^^
[12:02pm] anarcat: alright, i'll do this right away
[12:02pm] anarcat: other than that, i think that's it for me
[12:03pm] mig5: nothing new from me, all my time atm is taken up by work and study
[12:03pm] anarcat: alright, sounds like me except s/work and study/vacation/ 
[12:04pm] anarcat: mig5: @gmail is okay?
[12:04pm] mig5: sure
[12:04pm] omega8cc left the chat room. (Ping timeout: 240 seconds)
[12:04pm] You are now known as omega8cc.
[12:06pm] anarcat: okay, anyone else?
[12:06pm] anarcat: darthsteven: ping
[12:06pm] anarcat: omega8cc: how are the cron jobs?
[12:07pm] darthsteven: anarcat: pong!
[12:07pm] Irishgringo joined the chat room.
[12:07pm] anarcat: ha!
[12:07pm] anarcat: darthsteven: anything for the scrum?
[12:07pm] anarcat: darthsteven: we need to coordinate for the training and the session
[12:07pm] omega8cc: anarcat: it works great, but it should probably go in 1.3 no? as it is a critical for all users
[12:07pm] darthsteven: nothing for the scrum 
[12:07pm] anarcat: darthsteven: ok
[12:07pm] anarcat: darthsteven: i'm leaving the internets for a while on the 1st, so we would need to coordinate this week... email?
[12:08pm] anarcat: omega8cc: well, not for *all*, the drush method works fine right?
[12:08pm] darthsteven: anarcat: sure
[12:08pm] omega8cc: yeah, so it is critical in 50% 
[12:08pm] anarcat: okay
[12:08pm] anarcat: i don't think i'll be making a 1.3 release now
[12:09pm] anarcat: if someone else wants to, be my guest!
[12:09pm] omega8cc: as long as we have crush method as default, it is fine
[12:09pm] omega8cc: drush
[12:09pm] anarcat: univate: so the d7 port is handled by seth.vincent's sandboxes on drupal.org, if you want to followup on that it would be great
[12:09pm] omega8cc: uh, Lion autocorrection is crazy
[12:11pm] univate: anarcat: ok i will try and track down what is there
[12:11pm] anarcat: univate: can you give me your mail addy again
[12:14pm] univate: looks like seth.vincents last commits to his sandbox projects were 5 weeks ago
[12:15pm] anarcat: quite possible
[12:15pm] anarcat: he kinda stalled on the project at some point
[12:15pm] anarcat: i'll push him again now
[12:18pm] anarcat: so what's the next scrum time?
[12:18pm] welly left the chat room. (Quit: Textual IRC Client: http://www.textualapp.com/)
[12:18pm] anarcat: i won't be coordinating the next ones until october 1st
[12:19pm] anarcat: so we need someone to take that over, or we suspend those for a while
[12:19pm] mig5: I don't think we agreed on a new time, i'll coordinate with darthsteven / omega8cc
[12:20pm] mig5: if we can't agree on a good time we'll suspend them or rotate people
[12:20pm] anarcat: ok
[12:20pm] mig5: or i'll move to europe 
[12:20pm] omega8cc:                          
[12:21pm] omega8cc: it should be easy to find good time for EU/AU
[12:23pm] mig5: yeah
[12:24pm] jonhattan left the chat room. (Quit: llevaré una chaquete de guns'n'roses)
[12:24pm] anarcat: there was a time proposal here: http://community.aegirproject.org/discuss/new-scrum-time-our-gsoc-student
[12:28pm] omega8cc: mig5: what time works best for you? morning, evening?
[12:36pm] Egyptian[Laptop] joined the chat room.
[12:40pm] omega8cc: so maybe http://bit.ly/qGhjDr ?
[12:40pm] mig5: evening usually better for me
[12:41pm] omega8cc: 7, 8 or 9 pm?
[12:41pm] mig5: 8 or 9 is fine, that link above is fine with me
[12:41pm] mig5: let's see what darthsteven says
[12:41pm] omega8cc: k
[12:41pm] anarcat: mig5: ping
[12:41pm] mig5: pong
[12:42pm] q-rban left the chat room. (Remote host closed the connection)
[12:42pm] q0rban joined the chat room.
[12:43pm] anarcat:        http://community.aegirproject.org/handbook/project-history    
[12:44pm] mig5: that's quite good! when did that appear
[12:44pm] scientist joined the chat room.
[12:45pm] anarcat: i just wrote it
[12:45pm] mig5: nice
[12:45pm] mig5: some of that would be good in the wikipedia page
[12:46pm] mig5: (for those of you who missed it: http://en.wikipedia.org/wiki/Aegir_Hosting_System )
[12:46pm] anarcat: yeah, that's why i wrote it
[12:46pm] mig5:                          
[12:47pm] Irishgringo left the chat room. (Quit: ChatZilla 0.9.87 [Firefox 5.0.1/20110707182747])
[12:47pm] omega8cc: nice!
[12:48pm] mig5: in other news, i rejoined twitter, and now feel dirty
[12:49pm] mig5: and am studying for my OSCP, so if you find I discover any XSS or other holes in aegir, you know why  http://www.offensive-security.com/online-information-security-training/p...
[12:50pm] scottalan joined the chat room.
[12:51pm] darthsteven: mig5, omega8cc: 10AM UTC is fine with me
[12:52pm] omega8cc: mig5: I already grabbed that book about security thanks to your tweets, so it is a good thing (™)
[12:54pm] omega8cc: darthsteven, mig5: so let's change the scrum time to http://bit.ly/qGhjDr then for the summer
[12:54pm] darthsteven: agreed

20:00 <@mig5> ok, scrum time
20:00 <@mig5> as usual, no news from me this week :P
20:00 <@mig5> anarcat is away as we know
20:00 <@mig5> I have not heard from the GSOC student, so I will follow that up
20:01 <@mig5> there are currently no criticals in the queue which is nice, although I have vaguely heard about some issues with the cron queue, someone let me know if that's still an issue
20:01 <@mig5> aaaand I can't think of anything else significant, other than thanks to omega8cc for donating to hefring :)
20:02 <+omega8cc> haha
20:02 <@mig5> go for it darthsteven, omega8cc
20:02 <@darthsteven> I've done a little bit of work on the Aegir session for Drupalcon
20:02 <@darthsteven> hope to have that completed by the end of the week
20:02 <@mig5> oh nice
20:03 <@darthsteven> And then I hope to start writing docs again, but am away on holiday a lot over the next little while
20:03 <@darthsteven> but that's it from me
20:03 -!- aegir-jenkins [~PircBot@173-203-101-207.static.cloud-ips.com] has quit [Ping timeout: 252 seconds]
20:03 <@darthsteven> omega8cc?
20:04 <+omega8cc> I didn't submit any new patches, but I promise I will - related to the UI, soon
20:04 <+omega8cc> also, I released 1.0-boa-T-8.9, and it is using Aegir head
20:04 <+omega8cc> so good for receiving more feedback
20:05 <+omega8cc> and I noticed the sites cron is still an issue on some servers, when web based method is used
20:05 <+omega8cc> I will debug this and post more details soon
20:05 <@mig5> i am tired of this one in the queue: http://drupal.org/node/1111572 - I have been planning on removing a chunk of code from provision for that for a while, so I might do that in the 7.x branch and see how it goes
20:05 < hefring> http://drupal.org/node/1111572 => Undefined index: profiles deploy.provision.inc:84 => Provision, Code, normal, needs work, 14 comments, 2 IRC mentions
20:06 <@mig5> it is harmless but people keep carrying on about it
20:06 <@mig5> we have a fresh bug from ergonlogic too http://drupal.org/node/1236490
20:06 < hefring> http://drupal.org/node/1236490 => "View client" permission broken => Hostmaster (Aegir), Code, normal, active, 0 comments, 1 IRC mention
20:06 -!- aegir-jenkins [~PircBot@173-203-101-207.static.cloud-ips.com] has joined #aegir
20:07 <@mig5> aegir-jenkins returns.. that was weird
20:07 <@mig5> it's been up for over 100 days now, \o/
20:07 <@darthsteven> mig5: 1111572, can we set up a test case that invokes that code, remove it and then see if anything breaks/changes
20:07 <+omega8cc> aegir-jenkins: welcome back :)
20:07 -aegir-jenkins:#aegir- omega8cc did you mean me? Unknown command 'welcome'
20:07 -aegir-jenkins:#aegir- Use '!78jujdd7yujufyyshhayuuufhhysjjhyew9i2 help' to get help!
20:07 <@mig5> hah
20:07 <+omega8cc> haha
20:08 <@mig5> oops, and there goes anarcat's clever idea to 'hide' the jenkins command...
20:08 <@darthsteven> hehe
20:08 <@darthsteven> that's genius!
20:08 <@darthsteven> anyone else have anything for the scrum?
20:09 <@mig5> darthsteven: that's the thing re: test case: we don't scan packages in the site-specific dir, which means those values are always null. anyway i promise to look at it
20:09 <@darthsteven> ok
20:09 < Aciid> I have something , never setup a VM with Amazon AWS
20:09 <@mig5> ok, scrum done, unless ergonlogic has anything to add
20:09 < Aciid> http://pastebin.com/pRt4UNeg - mail sent by Amazon
20:10 <+omega8cc> so, thanks for attending!
20:10 <@mig5> cheers

[20:15:26]  <@darthsteven>  Scrum time
[20:15:30]  <@darthsteven>  at last!
[20:15:49]  <@mig5> yeah sorry about that
[20:15:52]  <@mig5> i have neglected it a bit
[20:16:14]  <@darthsteven>  ping: darthsteven, mig5, ergonlogic, grugnog, mvc, omega8cc, sfyn, skwashd (time for a scrum!)
[20:16:23]  <@darthsteven>  mig5: I kept forgetting to have them!
[20:16:33]  <@darthsteven>  do you want to go first?
[20:16:52]  <@darthsteven>  mig5: do you want to go first?
[20:17:04]  <@mig5> sure, that's easy: i've done nothing as usual
[20:17:06]  <@mig5> :)
[20:17:09]  <@omega8cc> lol
[20:17:13]  <@mig5> sigh
[20:17:26]  <@mig5> i want to look at getting those jenkins tasks into provision, but i haven't begun
[20:18:18]  <@mig5> i have built some cool automatic deployments using jenkins + aegir, all tracking changes in git, which i want to screencast soon
[20:18:28]  <@mig5> zero-touch deployment of dev > stage > live, good fun
[20:18:36]  <@darthsteven>  mig5: awesome!
[20:18:39]  <@mig5> anyway, that's me..
[20:18:57]  <@darthsteven>  mig5: Thanks!
[20:19:08]  <@darthsteven>  omega8cc: anything from yourself?
[20:19:27]  <@omega8cc> I already forgot what I did in the last few weeks :p but it was something, I'm sure! seriously, I probably helped with some drush issues and now working on a new theme, including mobile version for hostmaster
[20:19:46]  <@mig5> ooer
[20:19:53]  <@darthsteven>  cool! (the theme stuff, not forgetting things)
[20:20:21]  <@darthsteven>  omega8cc: anything else?
[20:20:50]  <@omega8cc> and the app for iOS and Android maybe is in the works, leveraging Aegir api where possible
[20:21:11]  <@omega8cc> but it is an Apple-like secret! lol
[20:21:44]  <@darthsteven>  heh, well the scrum logs don't get published anywhere ;)
[20:21:56]  <@omega8cc> but first, I will submit some simple UI related patches for the current theme
[20:22:02]  <@omega8cc> haha
[20:22:26]  <@omega8cc> I have some problems with it
[20:22:56]  <@omega8cc> I don't want to include ctools and stuff just to override some blocks, for example
[20:23:12]  <@omega8cc> so some patches will need to hit the core instead
[20:23:19]  <@omega8cc> I mean hostmaster
[20:23:40]  <@darthsteven>  omega8cc: ok, well I reckon we might end up with ctools in 7.x-2.x before long anyway
[20:23:58]  <@darthsteven>  because I want views in there :)
[20:24:09]  <@darthsteven>  omega8cc: anything else?
[20:25:06]  <@omega8cc> features_extra requires ctools, but we could too easily end up with fatcore instead of smallcore then
[20:25:08]  * skwashd stands up
[20:25:46]  <@omega8cc> so, features are nice, but always
[20:25:58]  <@omega8cc> but not* always, err
[20:26:28]  <@omega8cc> and that is it from me, I guess
[20:27:10]  <@darthsteven>  cool, thanks for the work on Aegir, as always
[20:27:17]  <@darthsteven>  skwashd: do you want to go next?
[20:27:45]  <@skwashd>  darthsteven: i have done 50% more work than mig5 on the same tasks as he has
[20:27:58]  <@skwashd>  darthsteven: and i plan to double my efforts on that task this week
[20:28:23]  <@mig5> that sounds believable
[20:28:30]  <@omega8cc> haha
[20:28:31]  <@darthsteven>  skwashd: sorry, what task was that?
[20:28:39]  <@mig5> trolling
[20:28:43]  <@skwashd>  darthsteven: doing fuck all for aegir
[20:28:46]  <@darthsteven>  heh
[20:29:07]  <@darthsteven>  well, thanks for keeping us in the loop :)
[20:29:16]  <@darthsteven>  skwashd: anything else?
[20:29:22]  <@skwashd>  mig5: i said i'd only done 50% more than you ... if we're talking about trolling there would be another 0 in there :P
[20:29:41]  <@darthsteven>  moving on...
[20:29:45]  <@darthsteven>  I'll go next
[20:29:46]  <@skwashd>  darthsteven: no
[20:30:06]  <@darthsteven>  I fixed an issue with PHP 5.2 and Drupal 7.8
[20:30:50]  <@darthsteven>  I've asked about spinning the theme out of hostmaster, back into it's own project http://drupal.org/node/1269212
[20:30:51]  <@hefring>  http://drupal.org/node/1269212 => Spin Eldir back out to its own project => Hostmaster (Aegir), Code, normal, needs review, 0 comments, 1 IRC mention
[20:31:17]  <@darthsteven>  I built a 'harness' for testing Eldir for Drupal 7: http://drupal.org/sandbox/darthsteven/1267494
[20:31:37]  <@darthsteven>  I.e. it's a 'port' of Hostmaster's HTML output for D7
[20:32:09]  <@darthsteven>  finally I have ported Eldir to D7: https://github.com/darthsteven/eldir
[20:32:23]  <@darthsteven>  building on the work of Seth (SoC student)
[20:33:00]  <@darthsteven>  I think I've also fixed various little things in Aegir and tried to process the queues a little
[20:33:42]  <@darthsteven>  Future plans are to possibly make the 7.x-2.x branch actually use D7, and begin the porting...
[20:34:05]  * beautifulmind has joined #aegir
[20:34:15]  <@darthsteven>  that's it from me
[20:34:22]  <@darthsteven>  anyone else?
[20:36:20]  <@darthsteven>  I'll give them a minute...
[20:37:46]  <@darthsteven>  </scrum>
[20:37:51]  <@darthsteven>  Thanks everyone!

20:01 <@darthsteven> scrum in 1 minute!
20:02 <@darthsteven> mig5, mvc, omega8cc, sfyn, skwashd; scrum in 1 min
20:03 <@darthsteven> scrum time!
20:03 <+omega8cc> hello!
20:03 <@darthsteven> scrum?
20:03 < hefring> scrum is Every Tuesday at 10h00 UTC: 03h00 San Francisco, USA (PST), 06h00 Montreal, Canada (EDT), 11h00 London, UK (CET), 20h00 Melbourne, Australia 
                 (EST)
20:03 <@darthsteven> indeed it is hefring
20:03 <@darthsteven> botsnack
20:03 < hefring> skynet thanks YOU!
20:03 <@darthsteven> who wants to go first?
20:04 <@mig5> just made it..
20:04 <@darthsteven> mig5: Hello!
20:04 <@mig5> you go firsst, you have been on fire in the queue!
20:05 <@darthsteven> I fixed some issues that were in the queue, and worked on the site form a little
20:05 <@darthsteven> Hopefully we can now handle database passwords that include special characters
20:05 <@darthsteven> though we may be chasing that one around a few more dark corners yet
20:06 <@darthsteven> I'd like some feedback about the site form changes (which are in a dev branch)
20:06 <@darthsteven> the issue is...
20:06 <@darthsteven> http://drupal.org/node/1282280
20:06 < hefring> http://drupal.org/node/1282280 => Clean up the hosting form javascript => Hostmaster (Aegir), Code, normal, needs review, 2 comments, 1 IRC mention
20:06 <@darthsteven> I would really appreciate some reviews of that
20:07 <@mig5> i never understood any of that as i don't grok javascript - i'm glad you're tackling it
20:07 <@darthsteven> It's basically just adding an AJAX spinner, so you know that something is happening...
20:07 <@mig5> so i'm not sure how helpful i can be there but hopefully others..
20:07 <@mig5> ah right
20:07 <@darthsteven> even just a test and 'I like the look of that' or 'Can we do this' would be helpful
20:08 <@darthsteven> Also
20:08 <@darthsteven> I installed Drupal 8 using Aegir last night, and it worked!
20:08 <@darthsteven> which isn't a major surprise, but it is fun
20:08 <@darthsteven> that's it from me
20:08 <@darthsteven> who wants to go next?
20:09 <@mig5> nothing from me, i see you want to add some drupal8 tests into jenkins, i can do that
20:09 <@mig5> still way too busy right now to look at moving tests into provision
20:09 <@mig5> hopefully more time early october when i go full-time consultant
20:10 <@darthsteven> mig5: do you have time for a quick chat after the scrum about Aegir stuff?
20:10 <@mig5> should do, it's either you or dinner, whatever happens first
20:10 <@mig5> :)
20:11 <@darthsteven> mig5: been thinking about the tests stuff, have some ideas and thoughts about it...
20:11 <@darthsteven> mig5: anything else to add?
20:11 <@mig5> nope, other than to say thanks to you specifically for working the issue queue like a nutter this week
20:11 <@darthsteven> mig5: thanks for coming to the scrum even if you don't have much to report!
20:11 <@mig5> keep it up but don't burn out :)
20:11 <@darthsteven> mig5: these are my normal levels of involvement in projects... :)
20:12 <@darthsteven> anyone else have anything for the scrum?
20:12 <+omega8cc> I don't have anything new related to the Aegir core this week to report, however I worked on some BOA new features and there is a chance I will submit some new patches for Nginx config (and finally) the menu/UI.
20:12 <+omega8cc> darthsteven: and also thanks for your work in the queue!
20:12 <@darthsteven> omega8cc: awesome!
20:13 <@mig5> omega8cc: i expect to hear you move into Linode Tokyo soon ;)
20:13 <@darthsteven> omega8cc: I think we should make tiding up the UI a priority for 2.x
20:13 <@mig5> sorry offtopic
20:13 <@mig5> apparently there was a drupal montreal on
20:13 <@darthsteven> anyone else?
20:13 <@mig5> i read some french tweets about it
20:13 <@mig5> something about an 'albert method', a guy from koumbit did a talk
20:14 <@mig5> i am keen to find out more, there are slides somewhere, search on twitter under #aegir
20:14 <@mig5> i think it's deployment-related, i'll see if i can find out more and get some english-language focus on it as it looked interesting
20:15 <@darthsteven> cool
20:15 <+omega8cc> http://t.co/gv7OisUe
20:15 <+omega8cc> or http://twitter.com/#!/omega8cc/status/114783126844223488
20:16 <@mig5> oh nice already in english
20:16 <+omega8cc> yep
20:16 <@mig5> again, soon, i will have a new screencast up
20:16 <@mig5> about my 'zero touch' deployment for aegir
20:16 <@mig5> using jenkins
20:16 <@mig5> that 'reacts' to git push in de/v/stage/live environments
20:16 <@darthsteven> mig5: cool, have you seen that someone is doing screencasts of Aegir stuff?
20:16 <@mig5> that will come 'soon' ;)
20:16 <@darthsteven> mig5: that would be awesome
20:16 <@mig5> darthsteven: yes i did, i watched one
20:17 <+omega8cc> mig5: cool! finally! :)
20:17 <@darthsteven> mig5: I've not watched them...so I've no idea if they're any good
20:17 <@darthsteven> To finish the scrum, I'd like to say...
20:18 <@darthsteven> that we seem to have had a bump in contributors, which is really cool!
20:18 <@mig5> yes! rock on, patchers!
20:18 <@darthsteven> There are also a few people who've started using Aegir, and are now blogging about the project
20:18 <@mig5> thanks GuyPaddock and halcyonCorsair
20:18 <@darthsteven> The 'Wedful' thing springs to mind
20:19 <@mig5> yes and hadsie, i think that was the first commercial 'payment' aegir system that implemented our api
20:19 <+omega8cc> right
20:19 <@darthsteven> So, with a bit of effort we make Aegir 2.x happen fast, and be super awesome in every way!
20:19 <@darthsteven> anyway
20:19 <@darthsteven> that's it for this scrum!
20:19 <@mig5> the pantheon project is getting a lot of publicity right now, i am keen to see people publish 'how to make your own pantheon' with aegir :)
20:19 <@mig5> just to balance things out :)
20:19 <@mig5> thanks scrummers
20:19 <@darthsteven> Thanks for attending
20:19 <+omega8cc> thanks
20:19 <@darthsteven> who wants to do the log thing?
20:20 <@mig5> i can
20:20 <@darthsteven> thanks!

[10:02am] darthsteven: mig5, ergonlogic, grugnog, mvc, omega8cc, sfyn: scrum time!
[10:02am] omega8cc: hello!
[10:02am] darthsteven: Welcome to our weekly Aegir Scrum
[10:02am] darthsteven: Who would like to go first?
[10:03am] merro left the chat room.
[10:04am] darthsteven: omega8cc: would you like to start us off?
[10:04am] beautifulmind joined the chat room.
[10:05am] omega8cc: darthsteven: all my nginx related new stuff is a bit delayed as it needs more testing
[10:05am] omega8cc: so I didn't submit any patches yet, but I hope to be able to do it this week
[10:06am] omega8cc: also new boa release has been delayed for this reason
[10:06am] darthsteven: okay
[10:06am] darthsteven: well, looking forward to reviewing those bits
[10:06am] merro joined the chat room.
[10:07am] darthsteven: anyone else?
[10:08am] darthsteven: I'll go next then
[10:08am] darthsteven: I factored out the Jenkins tests to a drush command in provision
[10:09am] darthsteven: so we can run them locally without python or Jenkins
[10:09am] darthsteven: which is nice
[10:09am] omega8cc: wow
[10:09am] darthsteven: We can also have different tests for the different branches now too
[10:10am] darthsteven: the tests are pretty basic, as we'll be using the Drush testing framework in a bit, when Drush 5 is out, but for now they're pretty basic
[10:10am] darthsteven: also
[10:10am] dfrt:  /t
[10:10am] darthsteven: I made the Jekins scripts use configuration from Jenkins, rather than new code in the repo
[10:11am] darthsteven: so we can do releases much more easily
[10:11am] darthsteven: speaking of which
[10:11am] darthsteven: We release 1.4 
[10:11am] darthsteven: *released
[10:11am] darthsteven: Fixing a security issue
[10:11am] darthsteven: Also
[10:11am] darthsteven: I created the 6.x-2.x branch, which was where the 7.x-2.x branch was
[10:11am] darthsteven: because...
[10:12am] darthsteven: 7.x-2.x now contains Drupal 7 code!
[10:12am] darthsteven: hurrah!
[10:12am] darthsteven: Porting is underway
[10:12am] omega8cc:
[10:12am] darthsteven: I was going to let everyone know via the community site, but couldn't because that had issues with the OA upgrade that was forced upon it
[10:12am] darthsteven: I will do that today though
[10:14am] omega8cc: darthsteven: so, is our gSoC student work/idea already cancelled, I suppose? as you are doing it currently
[10:14am] darthsteven: omega8cc: As far as I can tell, nothing really came of that
[10:14am] omega8cc: yeah 
[10:15am] darthsteven: we can always get him porting one of the modules if that's not the case
[10:15am] darthsteven: gSoC is over afaik anyway
[10:15am] darthsteven: Anyone else want to say anything?
[10:15am] omega8cc: so we may want to update our room header
[10:20am] szczym left the chat room. (Read error: Operation timed out)
[10:22am] omega8cc: darthsteven: Thanks for leading the work and our scrum! I can submit the log to c.a.o if you wish
[10:22am] darthsteven: end of scrum!

[21:00:33]  <@darthsteven>  anarcat, darthsteven, mig5, mvc, sfyn, skwashd: Scrum time!
[21:10:03]  <@mig5> sorry, nothing to report
[21:12:45]  <@darthsteven>  ok
[21:12:47]  <@darthsteven>  thanks!
[21:13:16]  <@darthsteven>  I applied some nasty patches to get the debian package installing correctly with drush 4.5
[21:13:46]  <@darthsteven>  I also got to the bottom of the problem when installing on debian, where it would consume all CPU and memory
[21:13:52]  <@darthsteven>  which anarcat then fixed!
[21:13:53]  <@mig5> excellent. do we need to roll a new release for that drush issue?
[21:14:57]  <@darthsteven>  I think we do
[21:15:08]  <@darthsteven>  I was going to add an issue to the queue
[21:15:20]  <@darthsteven>  See if we can do a release without anarcat :)
[21:15:58]  <@mig5> :)
[21:20:50]  <@darthsteven>  anyone else?
[21:21:06]  <@darthsteven>  speak now, or hold until next week...
[21:21:29]  <@darthsteven>  oh, and I just posted about changing the times of these: http://community.aegirproject.org/discuss/change-scrum-time
[21:36:06]  <@darthsteven>  okay
[21:36:13]  <@darthsteven>  official end of scrum there

[21:00:57]     Scrum time!
[21:01:00]     scrum?
[21:01:00]     scrum is Every Tuesday at 10h00 UTC: 03h00 San Francisco, USA (PST), 06h00 Montreal, Canada (EDT), 11h00 London, UK (CET), 20h00 Melbourne, Australia (EST)
[21:01:08]    go!
[21:01:19]     shall I go first?
[21:01:26]     okay, if you insist
[21:01:40]     Aegir 1.5 is out!
[21:01:42]     Hurrah
[21:01:47]    \o/
[21:01:57]     Anarcat helped in advisory role
[21:02:17]     which means at least two people can complete the full release process, independently
[21:02:26]    excellent
[21:02:50]     and we found that Jenkins actually does most of the work, and we could get it to do most of the rest of Debian stuff very easily
[21:02:57]     other things:
[21:03:10]     I did some bug fixes
[21:03:29]     I completely re-factored the 6.x-2.x branch of provision to use autoloading for classes
[21:03:41]     so we can support contrib add-ons for provision
[21:03:51]     I still need to document those changes
[21:04:01]     will try to get a few mins to do that today
[21:04:31]     also, I increased the number of things tested by Jenkins, and improved the quality of the code running the tests a little
[21:04:44]     resulting in less code all round :)
[21:05:05]     Also, made the upgrade tests take parameters
[21:05:09]     which is handy
[21:05:29]     also we now test PHP 5.2, every 24 hours if there are changes
[21:05:32]     that's it from me
[21:05:39]     mig5 want to go next?
[21:05:48]    ok - incredible efforts as always darthsteven, thanks
[21:05:52]    that's amazing work
[21:06:20]    me - very little as always - i simply built a new debian squeeze image with backported php 5.2 from lenny, so that we could do those php 5.2 tests
[21:06:57]    i'm pondering giving an aegir talk at http://drupaldownunder.org in January 2012, only a couple monts away now, but i'd like to diverge away from the usual 'how to install aegir, basic usage' thing we always do, as a lot of people will have seen that
[21:07:08]    any suggestions or ideas, let me know.
[21:07:11]    that's about it from me
[21:08:10]     mig5: thanks as always
[21:08:47]     anyone else?
[21:09:00]     mig5: we can chat talks after the scrum?
[21:09:23]    sure
[21:10:13]     anyone else? I'll give you a minute!
[21:11:31]     okay
[21:11:36]     thanks for attending mig5
[21:11:37]    i'll do log

07:01 <@mig5> well, scrum time :)
07:01 <@mig5> (I think!)
07:01 <@mig5> anarcat: ergonlogic: ^^
07:01 <@mig5> I'll start. I've got myself back into the swing of things a bit, fixed some minor bugs, accidentally even committed some fixes by mistake that I wanted 
              reviews of first, oh well :)
07:01 <@mig5> cleared out some old stuff in the queue that is irrelevant, are actually support requests, etc
07:02 <@mig5> submitted a talk for Drupal Down Under 
07:02 <@mig5> http://drupaldownunder.org/session/aegir-skynet-drupal
07:02 <@mig5> I'm making some stickers and tshirts for that conference to give away and generally spruik Aegir
07:03 <@mig5> welcome back darthsteven 
07:03 <@darthsteven> awesome stuff!
07:03 <@darthsteven> (my IRC reflector is doing funny things)
07:03 <@mig5> so, I'm hoping to continue to fix some small-ish bugs, help in the queue, etc
07:03 <@darthsteven> awesome stuff
07:03 <@mig5> i don't think i'll ever be a crazy big committer to the project since code is obviously not my biggest skill
07:04 <@mig5> but i'd like to get your help to make me contribute in some obvious way, even if it's just writing news/blog posts, managing the community portal etc
07:04 <@mig5> and perhaps be the '1.x' maintainer for basic bug fixes?
07:04 <@darthsteven> awesome, will try to push you :)
07:04 <@mig5> leaving you to concentrate on 2.x or something like that
07:04 <@mig5> these are just ideas anyway
07:05 <@mig5> anyway I think that's it for me. someone review my patches in the queue! :)
07:05 <@mig5> onto you darthsteven 
07:05 <@anarcat> hey
07:05 <@darthsteven> ok
07:05 <@darthsteven> hey hey
07:05 <@anarcat> yay, i didnt miss the scrum :)
07:05 <@mig5> yay!
07:05 <@anarcat> go ahead darthsteven :)
07:06 <@darthsteven> I didn't do too much this week, I did some issue queue re-assignment
07:06 <@darthsteven> I set up some Jenkins jobs to monitor code style of hosting and provision using the Coder review module
07:06 <@darthsteven> see: http://ci.aegirproject.org/view/Code%20reviews/
07:07 <@mig5> oh nice
07:07 <@darthsteven> not sure I'll have much time to work on stuff this week, but hoping to get back to 2.x asap
07:07 <@anarcat> nice
07:07 <@darthsteven> anarcat: over to you
07:08 <@anarcat> uh
07:08 <@anarcat> not much on my side either :)
07:08 <@anarcat> i am now a debian developer
07:08 <@mig5> \o/
07:08 <@anarcat> and so i have pushed ergonlogic's drush_make package into debian
07:08 <@anarcat> my glorious achievements can be seen here: http://qa.debian.org/developer.php?login=anarcat
07:09 <@anarcat> i will try to start working again on 2.x this week, as my replacement is coming to an end
07:09 <@anarcat> but it's not easy
07:09 <@mig5> you are not allowed to quit :)
07:09 <@anarcat> i have worked on 1.5 release last week a little and found a critical bug in the debian package, which hosed a client server here
07:09 <@anarcat> yeah
07:09 <@anarcat> but it's all fine now
07:09 <@anarcat> and we discovered that most of the debian build stuff is now automated by jenkins, which is freaking cool
07:09 <@anarcat> and i support mig5 as a 1.x maintainer
07:10 <@mig5> ouch. so that critical bug only affected the debian package?
07:10 <@anarcat> yeah
07:10 <@mig5> do we need to reroll? lots of people use it now
07:10 <@anarcat> http://community.aegirproject.org/1.5#Known_issues
07:10 <@mig5> ah
07:10 <@mig5> :)
07:10 <@anarcat> aka https://drupal.org/node/1328316
07:10 <@anarcat> it's been rerolled already
07:10 <@anarcat> i wouldn't have let that one sit there :)
07:10 <@mig5> right right
07:10 <@mig5> :)
07:10 <@anarcat> so next steps for me
07:10 -!- darthsteven_ [~darthstev@109.123.86.70] has joined #aegir
07:10 -!- mode/#aegir [+o darthsteven_] by ChanServ
07:10 <@anarcat> backport drush_make, once it hits tseting
07:10 <@anarcat> testing*
07:11 <@anarcat> look into merging the daemon into 2.x, the sites/ directory magic and unit testing
07:11 <@anarcat> those impatient to see drush_make hit testing/backports can reload franatically this page: http://packages.qa.debian.org/d/drush-make.html
07:12 <@anarcat> oh, and we have submitted a Aegir training proposal for Denver
07:12 <@darthsteven> good stuff anarcat
07:12 <@anarcat> so i guess that means we'll go to denver :)
07:13 <@anarcat> well, i think that's it
07:13 <@mig5> ok, anyone else?
07:13 <@mig5> ergonlogic ^^
07:13 <@anarcat> i think he's off
07:13 <@mig5> ok
07:13 <@anarcat> he was at drupalcamp toronto
07:13 <@anarcat> and is resting
07:13 <@mig5> oh that's right, i believe there was some aegir stuff happening there via him?
07:14 <@mig5> cool
07:14 <@anarcat> he presented aegir to some folks there and i heard through the grapevine that we may see derek again :)
07:14 <@mig5> who's derek?
07:14 <@anarcat> mig5: spiderman - worked on the dns stuff?
07:14 <@mig5> oh right!
07:14 <@mig5> I remember
07:15 <@mig5> ok, i'm off for breakfast. happy ot upload the log when i'm back in 20 min or so
07:15 <@mig5> thanks all!
07:15 <@anarcat> awesome
07:15 <@anarcat> yeah, i think that's it
07:16 <@darthsteven> thanks!
07:16 <@darthsteven> I think we need to do a 1.6 release for https://drupal.org/node/1330018 sooner rather than later
07:17 <@darthsteven> that bug is entirely my fault btw, major lack of testing on my part
07:17 <@anarcat> i see
07:17 <@anarcat> well, now you know how to make a release, maybe you can train mig5 to do it? :)
07:18 <@darthsteven> sure
07:29 <@darthsteven> I'll teach Jenkins how to do releases first

07:00 <@mig5> ok, time for a quick scrum
07:00 <@mig5> good morning
07:00 <@mig5> it appears darthsteven sends his apologies!
07:00 <@darthsteven> Nothing from me, will do a 1.6 release tomorrow if I have time!
07:00 <@mig5> so ping anarcat, ergonlogic, etc
07:00 <@mig5> oh he's here! :)
07:00 <@mig5> cool
07:00 <@mig5> thanks darthsteven 
07:00 <@darthsteven> Now I'm gone...
07:01 <@mig5> not much from me this week: I posted the first of a fortnightly Aegir newsletter last wednesday, I got some good feedback from anarcat but that was 
              about it :)
07:01 <@mig5> ok. 1.6 release will be tomorrow
07:01 <@mig5> my stickers have arrived, i ordered way too many for DrupalDownUnder, maybe I'll send some in the post to people :)
07:02 <@mig5> we fixed the Reset Password bug that broke resetting of passwords in Drupal 5, so that will go into the 1.6 release which is nice
07:02 <@mig5> that's all from me I think. anarcat?
07:03 < teeyza> so anyone have any ideas why my aegir wont upgrade?
07:03 <@mig5> right, i have a feeling anarcat isn't here, and we have a hijacker, so I might end the scrum earlier than usual..
07:03 <@mig5> thanks all
07:14 <@anarcat> oops
07:14 <@anarcat> missed the scrum
07:14 <+ergonlogic> sorry
07:14 <@anarcat> mig5 / darthsteven : pong
07:14 <@mig5> hehe
07:14 <@anarcat> we were in our own planning session over here, maybe we can touchbase on that
07:14 <@mig5> sure thing
07:15 <@anarcat> we are reorienting my work a bit, away from http://community.aegirproject.org/discuss/back-vacation
07:15 < teeyza> my apologies mig i was corrected, so were stuck on step 4 of the that link
07:15 <@anarcat> we'll focus on the debian packaging and puppet manifests
07:15 <@anarcat> i'm going to work on a provision-upgrade command which will be basically like drush upgrade
07:15 <@anarcat> but really safe
07:15 <@anarcat> and designed specifically with the upgrade of aegir itself in mind
07:16 <@anarcat> so that we can ship the files with the aegir-hostmaster package
07:16 <@anarcat> and overwrite existing files, and run the update and so on
07:16 <@anarcat> we're also going to work on D7 LDAP integration so that Drupal can be used to manage LDAP groups and user memberships
07:16 <@mig5> will that open itself up to http://drupal.org/node/711746 in any way?
07:16 < hefring> http://drupal.org/node/711746 => allow upgrade of hostmaster sites from the frontend => Hosting, Code, minor, postponed, 3 comments, 1 IRC mention
07:16 <@anarcat> which is a bit offtopic here
07:16 <@anarcat> mig5: i don't know
07:16 <@anarcat> maybe
07:17 <@mig5> we need that external queue daemon :)
07:17 <@anarcat> so those are our priorities, shifting the other ones in the list down
07:17 <@anarcat> yes
07:17 <@anarcat> so that's still in the list
07:17 <@anarcat> but probably after christmas if not summer
07:17 <@mig5> sure
07:17 <@anarcat> same with unit tests, which get pushed away
07:17 <@anarcat> we're going to also sponsor more uc_hosting and hosting_services development
07:18 <@anarcat> with sfyn waiting to do a lot of improvements there, apparently
07:18 <@anarcat> expect the "official puppet module for aegir" to come out soon
07:18 <@anarcat> oh
07:18 <@mig5> awesome! :) 
07:18 <@anarcat> and just random name-dropping here: openstack.
07:18 <@anarcat> that's it for me.
07:18 <@mig5> thanks anarcat
07:18 <+sfyn> 3~hey folks
07:19 <+sfyn> guess its scrum time
07:19 <@mig5> hey sfyn 
07:19 <+ergonlogic> for my part, I'll be helping with the aegir puppet module
07:19 <+ergonlogic> yeah... a little late
07:19 < teeyza> hey mig, you have any other suggestions i could try?
07:19 <@anarcat> sfyn: it *was* :)
07:19 <@mig5> teeyza: please wait a bit, we are in the middle of a regular meeting
07:19 <+ergonlogic> and otherwise continuing to push aegir-up towards a release
07:19 <+sfyn> oops
07:19 < teeyza> kk
07:19 <@anarcat> sfyn: we had a great discussion on prioritizing work for aegir in the following week here
07:19 -!- mode/#aegir [+m] by anarcat
07:20 -!- mode/#aegir [+v mig5] by anarcat
07:20 -!- mode/#aegir [+v darthsteven] by anarcat, anarcat
07:20 <@mig5> thanks..
07:20 <+ergonlogic> that's most of it for me
07:20 <+sfyn> short term my efforts are more on civicrm support right now
07:20 <@anarcat> sfyn: we'll be looking from feedback from you about estimates on how much time we should spend on hostnig_services integration this year
07:20 <@mig5> i'm very interested in the aegir puppet stuff, i use vagrant for dev now, let me know if you need extra eyes on that :)
07:20 <@anarcat> mig5: we certainly will!
07:20 <+ergonlogic> mig5: indeed, yes!
07:21 <@mig5> and i know puppet pretty well these days
07:21 <@anarcat> now that's cool
07:21 <+sfyn> anarcat: hosting_services is a mess right now
07:21 <@anarcat> sfyn: and yes, maybe we need to add provision_civi to our shopping list, if it's not budgeted in other teams
07:21 <@mig5> although ergonlogic taught me you can preseed directly in puppet, didn't know that :)
07:21 <+ergonlogic> :)
07:21 <@anarcat> sfyn: how much hours does that mean, "mess"? ;)
07:22 <+sfyn> anarcat: means i don't know
07:22 <@anarcat> sfyn: awesome
07:22 <@anarcat> sfyn: i've put a mostly random guess of 100h
07:22 <@anarcat> maybe we can try to fine-grain the thing in smaller iterations
07:22 <@anarcat> and do a better estimate
07:22 <@anarcat> but we don't need to do it now :)
07:22 <@anarcat> just a heads up that we'd like to push this out
07:22 <@anarcat> for the next reflexion meeting
07:22 <+sfyn> anarcat: ok
07:23 <@anarcat> alright, i think that's it for our part of the scrum, unless sfyn or ergonlogic have anything to add
07:23 <+sfyn> anarcat: I will break down the work for both projects over the week
07:23 <@anarcat> sfyn: awesome
07:23 -!- mode/#aegir [-m] by anarcat
07:23 <@mig5> thanks guys
07:23 <+ergonlogic> no, I'm done
07:23 <@anarcat> sorry for the censorship here :)
07:23 <+sfyn> thats it for me
07:23 <@anarcat> thanks\

[06:59:18]    <mig5>    scrum time in 1 minute i believe?
[06:59:25]    <mig5>    darthsteven: anarcat: ergonlogic:
[06:59:45]    <anarcat> oh yeah!
[07:00:04] <mig5>    ok!
[07:00:10]  <mig5>    scrum is now
[07:00:17] <anarcat> hi
[07:00:21]   <mig5>    i haven't done much this week at all :/
[07:00:29] * anarcat neither
[07:00:30]    <mig5>    and i just woke up so I can't remember if I did :)
[07:00:58]  <mig5>    well! if darthsteven doesn't show up, that's a very quick scrum! haha
[07:01:26]  <mig5>    I think ergonlogic worked on some new taxonomy/tagging/categorisation of discussion threads in the community site
[07:01:29]    <mig5>    i am yet to test it out
[07:01:40]  <mig5>    tomorrow i'll write my fortnightly aegir newsletter - do you think it should be monthly instead?
[07:02:04]    <anarcat> yeah
[07:02:05] <anarcat> makes sense
[07:02:17]  <anarcat> i was ill for two days last week, kinda knocked me off
[07:02:24]   <mig5>    the big news in it will be that 1.6 was released. speaking of that - we got a couple of good feedback on that release, and no big bug reports, so it must have been one of our most stable in a while
[07:02:30]    <mig5>    sorry to hear you were ill
[07:02:30]   <anarcat> cool
[07:02:47] <anarcat> i did some debian work on my side, and the more i think about it, the more i wish to package hostmaster properly...
[07:02:58]  <anarcat> i may work on that soon-ish
[07:03:04]  <mig5>    properly in what sense?
[07:03:10]  <mig5>    via debian official repos?
[07:03:15]   <anarcat> properly as in, with the php files actually in the package
[07:03:16]   <anarcat> yes
[07:03:32]  <mig5>    from memory we had some catch22 there
[07:03:35]    <anarcat> but that's further down the road
[07:03:42]    <anarcat> next step for me is ldap work
[07:03:43]    <mig5>    oh you mean with core inside it
[07:03:50]  <anarcat> yeah
[07:03:53] <mig5>    awesome
[07:04:04]  <anarcat> basically, this would mean that we would drun drush_make during the build, not during the install
[07:06:08]    <mig5>    right right
[07:06:16]  <anarcat> that's about it for me
[07:06:21]  <mig5>    thanks
[07:06:23]   <anarcat> let's wait another 10 to see if our friends show up
[07:06:27] <mig5>    yep
[07:06:44]  <anarcat> oh! ergonlogic wasn't voiced!
[07:06:50]   <mig5>    hahaha
[07:06:51]   <ergonlogic>  aha
[07:06:56]  <mig5>    geeeez us tyrants
[07:07:03]    <ergonlogic>  Hi all, sorry I'm late
[07:07:11]  <mig5>    hi!
[07:07:11]  <hefring> privet
[07:07:20]   <anarcat> hum
[07:07:41]  <mig5>    oh my site, and hefring, are now managed by Jenkins :) whaaaaat?
[07:07:52] <anarcat> ergonlogic: you do not seem to be identified with nickserv, which is why you are not voiced
[07:07:52]  <ergonlogic>  so, yeah I added a simpler tagging mechanism on c.a.o
[07:08:33]    <ergonlogic>  I normally am...
[07:08:34] <ergonlogic>  anyway, you can now tag without having to edit the node
[07:08:47]  <ergonlogic>  and we can filter discussions by keyword
[07:09:17] <mig5>    sweet *me goes and filters out all mention of centos/redhat* :)
[07:09:38]  <ergonlogic>  this was mostly in response to a suggestion by AquaticDisorder to have per-OS discussions
[07:09:46]    <ergonlogic>  exactly :)
[07:10:06]   <mig5>    hmm i search for 'centos' and i get no results
[07:10:13] <mig5>    same with 'debian'
[07:10:25] <ergonlogic>  are there any nodes tagged as such?
[07:10:30]  <mig5>    oh duh
[07:10:32]   <mig5>    probably not! :)
[07:10:49] <ergonlogic>  it's using the 'keywords' vocabulary
[07:10:55]  <mig5>    does it only search discussion threads?
[07:10:56]  <mig5>    gotcha
[07:11:00]   <ergonlogic>  which previously hadn;t been available for discussions
[07:11:04]   <mig5>    so it's probably that we have few tagged nodes
[07:11:04]  <mig5>    yep
[07:11:10]  <ergonlogic>  for now, just discussions
[07:11:17]    <mig5>    sorry still trying to wake up :)
[07:11:22] <ergonlogic>  :)
[07:12:00]   <anarcat> hey this reminds me - the twitter block seems to be broken
[07:12:07]   <mig5>    yeah was looking at that the other day
[07:12:08]   <anarcat> last post is from may or something
[07:12:09]   <mig5>    i can't work it out
[07:12:24] <mig5>    was looking at the view, but i think it's the feeds system itself... the feed URL is correct
[07:12:32]    <ergonlogic>  and I'm finally re-focusing on getting openatria.com running as a reference implemnetation of the Aegir-SaaS stack stuff I'd been working on
[07:12:33]   <mig5>    i think it's just not pulling in new items properly
[07:12:50] <anarcat> that sounds like a reasonable assumption
[07:12:54] <ergonlogic>  and expect an alpha release of aegir-up this week
[07:13:17]    <ergonlogic>  I can take a look at that
[07:14:34]    <ergonlogic>  re being identified... I switched to using a proxy, could that exaplain it?
[07:14:36]  <mig5>    maybe something for after the scrum: i noticed we can't install aegir on a non-standard port. eg port 8080 (for vagrant direct 8080 to 8080 mapping)
[07:14:57]    <mig5>    we totally ignore --http_port in hostmaster-install. not sure why, it *ought* to be trivial surely? (famous last words)
[07:16:42]  <ergonlogic>  mig5: re vagrant, at one point I had aegir set up with dns, and then just added my vagrantbox as a dns server in resolv.conf
[07:18:32] <mig5>    ah so you got arund the login links being port 80 etc by resolving them back to the vagrant machine itself, and the port 80 then NAT to the 8080 on the vagrant box too
[07:18:49]  <mig5>    i stil lreckon we should support non-standard port on fresh install: what if I want to put varnish in front of my aegir box for example
[07:18:54]  <mig5>    sure i can fiddle about after the install but yeah
[07:19:01]   <mig5>    anyway - i think we are done for scrum
[07:19:04]   <ergonlogic>  agreed
[07:19:07]   <mig5>    darthsteven appears MIA today
[07:19:13]    <mig5>    thanks all

[07:01:33]    scrum time - any devs here? anarcat: ergonlogic:
[07:01:38]     hey
[07:01:38]     eh oh
[07:01:39]     yes
[07:01:41]    I believe darthsteven is currently at a Drupal meetup
[07:01:44]    hello!
[07:01:44]     ni hao
[07:01:49]     very little for me again
[07:01:57]     i have released this nifty module that waglo wrote: http://drupal.org/project/dblogin
[07:02:16]    ooh interesting
[07:02:51]     Hello!
[07:02:51]     yo
[07:02:56]    very little from me too. i sent out a silly newsletter last wednesday to be in timing for Vertice's 1 year anniversary
[07:02:59]    hey darthsteven, you made it! :)
[07:03:03]     Nothing from me today, hoping to do some real work on Aegir soon though!
[07:03:09]     hey darthsteven
[07:03:18]     darthsteven: i was wondering - how is the d7 port?
[07:03:19]     mig5: Thanks for that
[07:03:32]     Hah, stalled
[07:03:45]     I have 0 time to spend on aegir at the moment
[07:03:49]     i see
[07:03:52]     i know your pain
[07:03:53]     That will change in Jan
[07:03:58]     cool
[07:04:12]     i note that ohloh thinks we have decreasing overtime development
[07:04:23]    probably true
[07:04:26]     I'm trying to convince my employer to sponsor some of my time on Aegir
[07:05:01]     Pretty much will be able to spend 1 day every three weeks
[07:05:18]     Sorry, I'll be quiet now.
[07:05:30]     ok
[07:05:36]     pretty much the same situation for me
[07:05:55]     so basically, we're looking for sponsors and workforce :)
[07:06:38]     Yup
[07:07:08]     I want to donate money to the project, can someone let me know how :)
[07:07:43]     don't we have a paypal account? :)
[07:07:59]    i think koumbit do ;)
[07:08:14]     ah right, that's what that button does
[07:08:31]     i wonder how many donatiosn we receive there
[07:08:36]    me too :P
[07:08:37]  * anarcat will take a look
[07:10:08]     the answer is 0$
[07:10:15]    whee
[07:10:28]    i thought i recalled ergonlogic or someone thanking some people in some release notes
[07:10:44]     interestingly enough, 6 of those are "incomplete transaction"
[07:10:59]     people donating between 18 and 100$ have canceled their submission, apparently
[07:11:10]    yeah 'http://community.aegirproject.org/1.3'
[07:11:11]    oh ok
[07:11:19]    weird
[07:11:35]     yeah
[07:11:37]     i wonder
[07:11:48]     i see my failed donation there, and it happened after i hit cancel in paypal
[07:11:54]     i'll try to do a real donation to see if it works
[07:13:20]    me too
[07:13:21]     this shit doesn't work
[07:13:28]    seemed to work for me
[07:13:29]     dude, did you just donate a lot?
[07:13:34]    $50
[07:13:43]     yeah
[07:13:47]     mig5: it says: En attente (Incomplete Transaction)
[07:13:49]    that's a lot?
[07:13:50]    hmm
[07:13:53]    that's no good
[07:13:54]     well, for a test :)
[07:14:18]    i got a transaction id but no confirmation email
[07:14:45]    it doesn't show up in my paypal activity though
[07:14:50]    so probably just didn't do anything
[07:15:15]     civicrm, i love you
[07:15:26]     so that button freaking doesn't work
[07:15:40]     ergonlogic: the donate button in the community site doesn't work
[07:15:57]     we should just create a paypal account for the project and be done with it, remove the koumbit intermediary
[07:16:09]    i think we'll need more dev hands on deck.. let's be honest.. devseed left us, and many others, in the lurch, and i don't think we ever fully recovered
[07:16:12]     mig5 / darthsteven : ... and then us three can share the access in some way
[07:16:22]    i wish i could code a bit better or i'd do it, but i don't think it's my strength
[07:16:38]     i agree we need more people
[07:16:45]     i will not comment on your skills, you never listen to me :P
[07:17:00]    will i git log | grep migression to make my point? :)
[07:17:22]    anyways. next month i am at Drupal DownUnder talking aegir, i'll try and evangelise and drum up dev interest
[07:17:29]    oh! how was Drupalcamp NYC, how did the session go?
[07:17:43]     the session went well!
[07:17:56]     i got to talk with the pantheon guys about how they do intersite security, it was really interesting
[07:18:10]    ah nice
[07:18:20]    are they in fact doing multisite?
[07:18:40]     yeah, they switched away from one vserver per site
[07:18:48]    interesting
[07:19:28]      not sure the context, but seeing pantheon and aegir in the same chat sounds exciteing
[07:19:54]    it's good to trade war stories :)
[07:20:13]     hehe
[07:20:20]     yeah, it was great
[07:20:33]    what amazes me about pantheon is the deliberate simplicity of it.. not too many features, quite spartan in its approach
[07:20:47]    you have to be good to avoid feature creep like that
[07:20:58]    anyways - shall we call that a scrum end?
[07:21:13]     yes, i think we're done

14:56       mig5@> shall we do a scrum darthsteven anarcat ergonlogic omega8cc
15:02    anarcat@> oh yes!
15:02    anarcat@> scrum time!
15:03   omega8cc+> hi!
15:03    hefring > privet
15:03    anarcat@> alright
15:04    anarcat@> well, for myself i am just back from vacation
15:04    anarcat@> still swamped with a lot of non-aegir related work
15:04    anarcat@> but hopefully i will get to fix some pesky issues that have been bothering our clients and workers here
15:05    anarcat@> one low hanging fruit we have is to deploy those module automatically on new sites: http://drupal.org/node/1157114
15:05    hefring > http://drupal.org/node/1157114 => DB Login => 0 comments, 1 IRC mention
15:06 (*)  anarcat looking for the second one
15:06    anarcat@> http://drupal.org/project/environment_indicator
15:06    anarcat@> there
15:06    anarcat@> the other things are: exportable backups and the pesky files directory
15:06    anarcat@> i am looking for ways to optimise the migrations
15:06    anarcat@> because right now we end up tarring and untarring a lot of the same crap every week
15:07    anarcat@> and i'm looking for ways to optimise that
15:07    anarcat@> so suggestions welcome there
15:07    anarcat@> the exportable backups is just to have a way to hardlink the backup in the @hostmaster/files directory with a hard-to-guess filename so that only the user can download it
15:11       mig5@> interesting
15:11       mig5@> sorry, dealing with a nagios alert here at the same time
15:11    anarcat@> fun :)
15:11    anarcat@> i think that's pretty much it for me
15:12       mig5@> not much from me this week.. need to find some more time to look at http://drupal.org/node/1388906 again. would be nice to test the nginx stuff more, not that we don't trust omega8cc of course :)
15:12    hefring > http://drupal.org/node/1388906 => It is possible to break Nginx based install with upload progress by enabling nginx_ssl feature => Provision, Code, critical, needs review, 5 comments, 1 IRC mention
15:12       mig5@> i'm otherwise just swamped with work, it's insane
15:12    anarcat@> i know how you feel
15:12    anarcat@> my return from vacation is insane
15:12       mig5@> i give my aegir talk at Druapl DownUnder on saturday, should be good
15:12       mig5@> how was NYC ?
15:12    anarcat@> we had a compromised ftp account that sent out 30k spams on my first day :P
15:12       mig5@> ugh!
15:12    anarcat@> it was good
15:12    anarcat@> it was only one day!
15:12    anarcat@> but i did a aegir pres with ergonlogic
15:12    anarcat@> and i think we got a few people in
15:13    anarcat@> i met with the pantheon guys, and they have a *great* product
15:13    anarcat@> not open source of course :P
15:13       mig5@> yeah. it's nice and simple
15:13    anarcat@> but they really got somethign going with their dev/staging/prod thingy
15:13       mig5@> yes and non-free :(
15:13 ergonlogic > hi
15:13    anarcat@> well, i got invite codes
15:13    anarcat@> i promised josh_k_ i would try to crack their thing
15:13       mig5@> haha
15:13    anarcat@> so far didn't find the time
15:13    anarcat@> but they really have good security tools
15:14    anarcat@> they are using cgroups, fcgi (or similar)
15:14       mig5@> David Strauss knows his stuff
15:14    anarcat@> so basically, you are renting out process groups
15:14       mig5@> and that valhalla filesystem he's using for clustering and HA, sounds interesting
15:14    anarcat@> as opposed to whole vservers, which was the old way
15:14    anarcat@> yeah that's nice too
15:14       mig5@> what are they using underneath: debian?
15:14       mig5@> or redhat?
15:14    anarcat@> i didn't troll, so i don't know ;)
15:14       mig5@> i seem to recall a redhat feature that rented processes
15:15    anarcat@> well, cgroups allow for fine-grained process isolation
15:15    anarcat@> cgroups is the kernel option that allows vservers (or linux containers as the call them now) to work
15:15       mig5@> yeh
15:15    anarcat@> they also use selinux
15:15    anarcat@> they seem really into it
15:15    anarcat@> pretty cool
15:15    anarcat@> anyways
15:15       mig5@> i'm surprised they don't just build a machine per client or something.. it's not that expensive these days
15:15    anarcat@> enough with pantheon :P
15:15       mig5@> yeah :)
15:15    anarcat@> mig5: that's what they were doing before
15:16    anarcat@> i think it was *more* expensive than clustering in a single box
15:16    anarcat@> you got to get some edge in some place
15:16    anarcat@> so anyways
15:16    anarcat@> ergonlogic hi!
15:16    anarcat@> ergonlogic: something to add to our first scrum of the year?
15:16    anarcat@> (or is it?)
15:16    anarcat@> :)
15:16 ergonlogic > well, I'm just back from vacation too
15:16    anarcat@> welcome back :)
15:17 ergonlogic > so trying to get back into the swing of things
15:17 ergonlogic > I'm working out the kinks to start doing to Aegir 101 screencasts
15:17 ergonlogic > s/to/some/g
15:17 ergonlogic > and fighting with vimeo... they don;t like .ogv apparently
15:18    anarcat@> them basterds :)
15:18 ergonlogic > but anyway, just "how to create a site with Aegir" kinda stuff
15:18 ergonlogic > introductory for new clients, at this point
15:19 ergonlogic > other than that, just before the holidays, anarcat and I published a couple puppet modules
15:19 ergonlogic > one for drush and another for aegir
15:19 ergonlogic > on d.o
15:19    anarcat@> oh yeah we did!
15:19    anarcat@> actually *you* did :)
15:19 ergonlogic > well, I published them, sure...
15:19    anarcat@> but yeah, we polished a aegir module
15:19 ergonlogic > but *we* worked on getting them publishable
15:19    anarcat@> unfortunately it still relies on debian
15:19    anarcat@> ie. it doesn't do the manual install if you're *not* on debian
15:19       mig5@> oh, exciting! where are the modules?
15:19    anarcat@> which would have been awesome
15:20 ergonlogic > I posted a dozen or so issues on them for cleanup 
15:20    anarcat@> well, it *should* be on http://community.aegirproject.org/contrib-modules
15:20    anarcat@> but it isn't :P
15:20       mig5@> i'll work this into a new aegir newsletter :)
15:20 ergonlogic > I'll get the urls
15:20    anarcat@> and i'll add them to the page
15:20 ergonlogic > http://drupal.org/project/puppet-aegir
15:20 ergonlogic > http://drupal.org/project/puppet-drush
15:21       mig5@> i love this: server goes down, hosting company's support system and all their nameservers go down as well. excellent
15:21       mig5@> if it wasn't for DNS cache they'd be uncontactable to tell them about it
15:21 (*)  anarcat notices the twitter block on c.a.o is still broken
15:21 ergonlogic > they depend on a couple other puppet modules, one from Koumbit, and another from RiseUp, which is documented on the project pages
15:21    anarcat@> mig5: dns -> ouch
15:21 ergonlogic > sigh...
15:21       mig5@> great stuff re: puppet
15:22       mig5@> looking forward to trying that
15:22 ergonlogic > anyway, I also updated Aegir Up to use the new puppet modules
15:22 ergonlogic > http://drupal.org/project/aegir-up
15:22 ergonlogic > using git subtrees
15:22    anarcat@> mig5: another thing for your newsletter: arch linux support! http://community.aegirproject.org/node/389/revisions/view/2683/2684
15:23       mig5@> yes! saw that
15:23 ergonlogic > so I now have about a dozen branches to wrangle
15:23       mig5@> and did you see darthsteven's crazy article where he mass-migrated sites between two aegirs
15:23 ergonlogic > but seems more maintainable than sub-modules
15:23 ergonlogic > indeed yes!
15:23 ergonlogic > I want to try it out this week or next
15:24 ergonlogic > the mass migration stuff looks very cool
15:24 ergonlogic > it's also the initial reason I started aegir-up, to test that sort of thing
15:25    anarcat@> http://community.aegirproject.org/contrib-modules#Puppet_modules
15:25 ergonlogic > anarcat: thanks!
15:26 ergonlogic > I think that's it from me...
15:26    anarcat@> ok, i think we're done then
15:27   omega8cc+> I'm also back at work and plan to port some never submitted patches to 1.x, as we (boa) are using already 2.x code so it was a bit out of sync between boa and official Nginx support in Aegir 1.x
15:27 ergonlogic > I'd really appreciate some feedback on Aegir-up, btw
15:27    anarcat@> unless darthsteven magically flys in
15:27    anarcat@> with his cape
15:27    anarcat@> oh, omega8cc ! hi! :)
15:27   omega8cc+> plus, I promised to submit standalone Aegir on Nginx how-to (step by step). We also tested and helped to fix a few distros so they work with Aegir and this list grows nicely :)
15:27   omega8cc+> hi anarcat! and all
15:27    anarcat@> nice!
15:27    anarcat@> omega8cc: any work on a debian package for nginx? :)
15:28   omega8cc+> anarcat: there is chance it will be soon! on the table already
15:28   omega8cc+> as we are moving with everything to things like deb, puppet etc
15:28 darthsteve@> Sorry I missed the scrum!
15:28    anarcat@> nice!
15:28 darthsteve@> In another meeting
15:28    anarcat@> i am really happy to hear that!
15:29    anarcat@> omega8cc: if you need help with the package, i already have ideas on how to do it
15:29 darthsteve@> Nothing really to add though
15:29 ergonlogic > omega8cc: I'd be happy to integrate nginx patches to the puppet-aegir module :)
15:29 ergonlogic > hi steve
15:29    anarcat@> omega8cc: basically, i think that it can be done without creating a new package - just add "| nginx" as a dependency and make a debconf dialog (or autodetection) to figure out which to setup
15:29 ergonlogic > steven
15:29   omega8cc+> anarcat: I will ask for your assistance for sure, thanks!
15:29 darthsteve@> Hoping to get back to working on Aegir within the next few weeks.
15:29 darthsteve@> Sorry for interrupting!
15:30   omega8cc+> anarcat: exactly, it shouldn't be a separate package
15:30 ergonlogic > darthsteven: thanks for the mass migration write-up
15:30    anarcat@> cool
15:30 ergonlogic > darthsteven: I'll be trying it out soon
15:30   omega8cc+> ergonlogic: sure, I will let you know
15:31 darthsteve@> ergonlogic: Yeah, no doubt I removed a vital part of it while writing it up. Pester me of that's the case
15:31 ergonlogic > darthsteven: you can bet on it ;)
15:32 darthsteve@> Some of it will be in Aegir core at some point, so I'd rather find the bugs now :)
15:33   omega8cc+> darthsteven: hi, in the meantime we (boa) are testing the 2.x code in production :)
15:34   omega8cc+> so far, absolutely no issues
15:34 darthsteve@> omega8cc: Hehe, just you wait...
15:35   omega8cc+> ;)
15:35 darthsteve@> omega8cc: Though hopefully we can get some more tests written
15:40 ergonlogic > ok then... so, I'll assume that's the end of the scrum and post the log to c.a.o
15:40       mig5@> thanks ergonlogic

14:59 darthsteve@> scrum in a couple of mins
15:02 darthsteve@> mig5, anarcat, EclipseGc, ergonlogic, hadsie, mvc, omega8cc, sfyn, skwashd: scrum!
15:04    anarcat@> yay!
15:04    anarcat@> i'm here for once
15:04 ergonlogic+> hi there
15:04    anarcat@> hey ergonlogic
15:04   omega8cc+> hi
15:04     hadsie+> hey
15:04    hefring > eh oh
15:05    anarcat@> alright, should i start? i have lots to say :)
15:05    anarcat@> so i'll just go ahead
15:05 ergonlogic+> sure
15:05    anarcat@> alright
15:05    anarcat@> i wrote this crazy web_pack module last week
15:05    anarcat@> in basically 3 hours, i fixed most of the issues i was having with our multi-server support, or at least the "cluster" use case
15:06    anarcat@> i have posted this article requesting comments for total replacement of the current cluster module with the new implementation:
15:06    anarcat@> http://community.aegirproject.org/discuss/are-people-using-cluster-modul...
15:06    anarcat@> s/#comment.*//
15:06    anarcat@> anyways
15:06 darthsteve@> cool
15:06    anarcat@> the idea is to stop syncing the damn platforms and sites all over the place all the time
15:06    anarcat@> we only sync the ~aegir/config directory and reload apache
15:06 darthsteve@> replace replace replace
15:07    anarcat@> we assume /var/aegir/platforms is NFS-mounted
15:07    anarcat@> which brings me to: i think we should install the hostmaster platform in /var/aegir/platforms
15:07    anarcat@> it's inconsistent to have it where it is, and i don't see what purpose it serves
15:07    anarcat@> + it makes sharing "all the platforms" harder
15:07    anarcat@> food for thought
15:07    anarcat@> i have also worked on the provisionacl module
15:07    anarcat@> to make the sites directory accessible to the client group
15:08    anarcat@> but there are a few snafus in there that need working out
15:08    anarcat@> basically: http://drupal.org/node/1428526
15:08    hefring > http://drupal.org/node/1428526 => Files created by www-data user => Provision ACL support, Code, normal, active, 0 comments, 1 IRC mention
15:08    anarcat@> and http://drupal.org/node/1416056
15:08    hefring > http://drupal.org/node/1416056 => give access to entire site directory (was: add support for .git) => Provision ACL support, Code, normal, active, 8 comments, 1 IRC mention
15:08    anarcat@> otherwise i am trying to think more about how to optimise the migrate task so that it doesn't tar and untar all those damn files all the time
15:09    anarcat@> so far i came up with the idea that files/ should be a symlink to a version-controlled storage
15:09    anarcat@> and that therefore shouldn't eb backed up
15:09    anarcat@> so backups would now mean "backup the database", not "backup the filesystem"
15:09    anarcat@> that would be a plugin, i guess
15:09    anarcat@> i had a bit more time to work on aegir these days, which feels good
15:10     hadsie+> that would be awesome :)
15:10 darthsteve@> hmm…interesting
15:10    anarcat@> especially since it's client work paying for that
15:10    anarcat@> looking for more of those opportunities here
15:10    anarcat@> oh and i had issues... with 2.x
15:10    anarcat@> i wrote the pack module for 2.x, but since we don't deploy 2.x anywhere, i had to backport it to 1.x, which means now i have 4 branches (2 per module, 2 per version) for this simple module
15:11    anarcat@> kind of stupid
15:11 darthsteve@> ouch
15:11    anarcat@> i also wonder if that module could just be contrib, i didn't bother
15:11    anarcat@> i think that's it for me
15:11 darthsteve@> well looks like you got up to lots of stuff
15:11 darthsteve@> thanks!
15:11    anarcat@> :)
15:11 darthsteve@> anyone else want to go next?
15:12 ergonlogic+> you?
15:12 ergonlogic+> ok, me then
15:13 darthsteve@> ergonlogic: you go
15:13 ergonlogic+> I've been mostly working on Open Atrium features these past couple weeks
15:13 ergonlogic+> and not enough on Aegir
15:13 darthsteve@> tut tut
15:13 ergonlogic+> but that should change soon, as I gear up to launch openatria.com
15:13 darthsteve@> oh cool
15:13 ergonlogic+> I'll basically be solidifying the contrib modules I've written
15:14 ergonlogic+> but that ususally involves some patches to aegir too
15:14 ergonlogic+> I also nee to update aegir-up, as an update to vagrant has now broken it
15:14 ergonlogic+> and I realized that at least 2 people other than myself were using it
15:14 ergonlogic+> so that'll be a priority this week
15:15 ergonlogic+> and I'll be reworking our puppet modules
15:15 ergonlogic+> mostly to parameterize the classes
15:15 darthsteve@> awesome
15:15 (*)  anarcat notes that vagrant has now hit debian unstable, which means he may start using it... some day :P
15:15 darthsteve@> need to talk to you about those puppet modules...
15:15 ergonlogic+> so we can point to other db servers, etc.
15:15    anarcat@> darthsteven: can do
15:15 ergonlogic+> darthsteven: whenever you'd like
15:16    anarcat@> snap :)
15:16 ergonlogic+> anyway, that's my plan for the coming weeks
15:16 darthsteve@> cool, thanks also
15:16    anarcat@> alright, we're splurging out of our timebox here
15:16    anarcat@> anyone else?
15:16 ergonlogic+> oh, and I'd like to get back to screencasting, but that'll probably have to wait
15:16 darthsteve@> me!
15:16    anarcat@> go go ! :)
15:16 darthsteve@> I've been working on something called 'Pergola'
15:16 darthsteve@> which is an open source version of the Pantheon server setup scripts
15:17 darthsteve@> using puppet
15:17 darthsteve@> so not much Aegir time
15:17    anarcat@> whoa
15:17 darthsteve@> but, been trying to get back into Aegir stuff
15:17    anarcat@> "A pergola, arbor or arbour is a garden feature forming a shaded walkway, passageway or sitting area of vertical posts or pillars that usually support cross-beams and a sturdy open lattice, often upon which 
                   woody vines are trained. As a type of gazebo, it may also be an extension of a building, or serve as protection for an open terrace or a link between pavilions."
15:17    anarcat@> - wikipedia
15:17 darthsteve@> and think about the D7 port and 6.x-2.x etc.
15:17    anarcat@> pergola isn't aegir driven?
15:18 darthsteve@> also, I did a migration the other day that failed in a really horrible way
15:18 darthsteve@> which was interesting
15:18    anarcat@> indeed
15:18    anarcat@> horrible as in killing kittens?
15:18 darthsteve@> Will talk about Pergola after the scrum, mentioned it, because that's where I've been spending my time :)
15:18    anarcat@> ok
15:18 darthsteve@> horrible as in the apache config got rolled back, but the site's files did not
15:19    anarcat@> we should talk about [67].x-2.x after too
15:19    anarcat@> ouch
15:19 darthsteve@> I had a look at Pantheon and dev cloud for inspiration for getting Aegir easier to use
15:19 darthsteve@> seeing how/if they handle 'platforms' and 'sites'
15:19    anarcat@> yeah, they really have their shit together
15:20 darthsteve@> but that's it from me
15:20 darthsteve@> anyone else?
15:20    anarcat@> hadsie ? omega8cc ?
15:20    anarcat@> don't be shy, we'd love to hear you talk about your aegir work! :)
15:20   omega8cc+> I have a ton of patches collected for nginx config, ready to submit, but who will have a time to review them? mig5 maybe? :)
15:20   omega8cc+> Anyway, it is a first step to fully (finally) sync my already fork with upstream before I will be able to seriously get the .deb thing done for nginx folks right, which is the next step to get done.
15:21    anarcat@> if they're marked as needs review, i may just do that, because i'm considering a 1.7 release with the pack module :)
15:21    anarcat@> nice, we should talk
15:21   omega8cc+> ok,  expect a flood there :)
15:21   omega8cc+> And that is it from me, I guess.
15:21    anarcat@> alright
15:21    anarcat@> so unless hadsie or anyone else has something to add, i guess we can close this scrum
15:21    anarcat@> and thank you everyone for attending!

[06:59:17]    <anarcat> scrum?
[06:59:17]   <hefring> Every Monday at 20h00 UTC: 12h00 San Francisco, USA (PDT), 15h00 Montreal, Canada (EDT), 20h00 London, UK (GMT), 07h00 (Tuesday) Melbourne, Australia (EST)
[07:00:10]  <ergonlogic>  hi all
[07:00:46]   <darthsteven> hi all!
[07:00:54]  <anarcat> hi
[07:00:54]   <hefring> what's up
[07:01:22]   <anarcat> so i can start i guess
[07:01:30]   <anarcat> i have worked a bit more on aegir in the last week
[07:01:40]   <anarcat> i have merged the pack branch into 1.x and 2.x
[07:01:47]   <anarcat> assuming that it was okay to ship 1.7 with it
[07:01:59]    <anarcat> i am working on the import documentation today
[07:02:11]   <anarcat> what else
[07:02:19]    <anarcat> oh, i want to merge the debian branch into 1.x and 2.x
[07:02:23]   <anarcat> so that we can start building 2.x packages
[07:02:38]   <anarcat> we need to figure out *where* they would be uploaded, because that would override the 1.x packages
[07:02:46]   <anarcat> but maybe we can just make another reprepro archive or something
[07:03:06] <anarcat> what else what else
[07:03:22]  <anarcat> oh
[07:03:31]   <anarcat> i would really like to see us switch to vagrant for jenkins
[07:03:35]  <anarcat> but i have no time to take care of it
[07:03:45]    <anarcat> i am tired of false positives and i'd like to be able to test aegir with vagrant
[07:03:58]    <anarcat> vagrant should hit debian testing this week, so i'll install it at hme and may start playing with it
[07:04:09]    <anarcat> other than that, don't count on me for vagrant stuff too much :)
[07:04:12]    <anarcat> alright, that's it for me
[07:04:36]   <ergonlogic>  k, thanks anarcat
[07:04:43]    <ergonlogic>  I'll go next
[07:04:54]    <anarcat> http://community.aegirproject.org/content/content/administrator/post-ins...
[07:04:58]  <anarcat> go!
[07:05:10]  <ergonlogic>  I've updated aegir-up to run on the latest vagrant (0.9.8)
[07:05:28]  <ergonlogic>  and I've been using it to improve the puppet-aegir module
[07:06:00]   <ergonlogic>  so, I have plenty of experience with aegir running on vagrant, but none w/ Jenkins
[07:06:40]   <ergonlogic>  I've been poking around a bit
[07:07:17]   <darthsteven> cool beans
[07:07:24]   <ergonlogic>  but I'd prefer to help someone with more jenkins experience, rather than try to do it myself
[07:07:50]    <ergonlogic>  anyway, we can now specify all the hostmaster variables in the puppet module
[07:08:00] <ergonlogic>  and I'm currently working on supporting manual installs
[07:08:18] <ergonlogic>  and I'm stuck at 'hostmaster-install' but I think I see a light at the end of the tunnel
[07:08:29]  <ergonlogic>  that's pretty much it for me
[07:09:11]    <darthsteven> me next
[07:09:19]  <darthsteven> I've had some time to fix some bugs!
[07:09:21]    <darthsteven> yey!
[07:09:37] <anarcat> yay!
[07:09:41] <darthsteven> so 1.7 will have many fewer notices in the logs
[07:09:57]  <darthsteven> and the site form now works in Internet Explorer
[07:09:58] <darthsteven> :)
[07:10:01]   <anarcat> wow
[07:10:04]  <ergonlogic>  nice
[07:10:04] <anarcat> incredible
[07:10:07]   <anarcat> IE6? :P
[07:10:12]  <darthsteven> fixing some more simple bugs tonight
[07:10:17] <darthsteven> hah!
[07:10:19] <darthsteven> not likely
[07:10:21]   <anarcat> sorry for the swearing ;)
[07:10:29]    <anarcat> should we look at releasing 1.7 soon?
[07:10:30]    <darthsteven> that's it from me
[07:11:17]   <anarcat> it seems that omega8cc has a few patches sitting in the queue, i think mig5 looked at a few of those, but we should probably factor them in
[07:11:37]  <anarcat> also, it seems to me that we should punish omega8cc with commit access, for too long they have been submitting good patches for nginx ;)
[07:11:37] <ergonlogic>  if we do a 1.7 soon, I'd suggest we stick with Drupal 6.23, as 6.24 seems to have a couple bugs
[07:11:46] <anarcat> crap
[07:12:11] <omega8cc>    heh, I'm still in the 'port hundreds of Nginx config changes from BOA fork to Aegir 1.x and 2.x' phase.
[07:12:14]   <omega8cc>    I didn't realize how far it got, but we will get it back in sync with our dear upstream again :)
[07:12:26]    <anarcat> i am happy to hear that! :)
[07:12:30]  <omega8cc>    We are almost there, anyway.
[07:12:42] <anarcat> i am especially curious to see that "no create content stupid submenu" patch :)
[07:12:48]    <omega8cc>    6.24 is fine with two patches
[07:12:52]    <anarcat> that would be a great improvement
[07:13:03]    <omega8cc>    yeah
[07:13:05] <anarcat> we could ship with patches to the makefile...
[07:13:45]    <anarcat> alright, anyone else?
[07:13:50]    <ergonlogic>  If we're going forward with a 1.7, I'll post an issue to track it
[07:14:16]  <ergonlogic>  omega8cc: if you could comment there with the patches, that would be great
[07:14:30]   <anarcat> ergonlogic: let's
[07:14:37]   <ergonlogic>  I'm on it
[07:15:06]   <anarcat> alright, anyone else has something to add to our scrum?
[07:15:16]  <anarcat> otherwise i think we're done, thanks everyone for your attention
[07:15:57]    <omega8cc>    ergonlogic: basically: https://github.com/omega8cc/pressflow6/commit/97b8df2795e9565ffff5dcaa00... and https://github.com/omega8cc/pressflow6/commit/4b05a210c4234714104149c3ef...
[07:16:40]   <omega8cc>    there are two major issues only, both listed at http://drupal.org/drupal-7.12
[07:16:41]    <anarcat> omega8cc: are those patches upstream?
[07:16:48]    <ergonlogic>  http://drupal.org/node/1439120
[07:16:48]   <hefring> http://drupal.org/node/1439120 => Release 1.7 => Hostmaster (Aegir), Code, normal, active, 0 comments, 1 IRC mention
[07:17:35]   <ergonlogic>  I'll post the scrum log to c.a.o

20:06 <+omega8cc> scrum?
20:06 < hefring> Every Monday at 20h00 UTC: 12h00 San Francisco, USA (PDT), 15h00 Montreal, Canada (EDT), 20h00 London, UK (GMT), 07h00 (Tuesday) Melbourne, Australia (EST)
20:08 <@mig5> oops
20:08 <@mig5> in an hour i think?
20:08 <+omega8cc> no, now! :)
20:09 <+omega8cc> mig5: is this 21h00 in Melbourne, Australia (EST)?
20:09 <@mig5> hmm, it's 20h00 here
20:09 <+omega8cc> heh
20:09 <+omega8cc> so we need to fix this http://community.aegirproject.org/scrums
20:09 <@mig5> maybe i moved back and the rest of you stayed where oyu are
20:09 <+omega8cc> as it says 12h00 (noon) in Warsaw, Poland
20:09 <@mig5> now is fine, if that's the normal time
20:09 <@mig5> i think i must've moved back
20:09 <@mig5> so it was EDT before
20:10 <@mig5> ok, scrum :P
20:10 <+omega8cc> ah
20:10 <@mig5> i have nothing to add anyway!
20:11 <+omega8cc> Nothing new to report from me today, but I do have an idea I want to discuss later.
20:11 <+omega8cc> We have some concept-grade, half-baked modules for importing the site into Aegir (or migrating between Aegir instances), plus many how-tos etc. But what we really need is an aegir_connector, like in this demo: http://vimeo.com/41020017 This is what I want to get done right in the next month or two.
20:13 <+omega8cc> mig5: so we need to fix the hours at http://community.aegirproject.org/scrums as it should much your time when it is a good time in AU
20:13 <+omega8cc> match*
20:13 <@mig5> now is fine, i'll just change melbourne's time
20:14 <+omega8cc> ok
20:15 <@mig5> i can only add that i played with the Pack module and managed to get it working. i think the docs for Pack need a lot of work, and there are some 'gotchas' such as the aegir UID/GID needing to  match between systems or aegir fails to chmod/chown during rsyncs etc
20:15 <@mig5> and, i wrote some neat Jenkins/Fabric magic that automatically tags install profile repositories and updates stub makefiles and does tag-based deployment with drush make etc
20:15 <@mig5> for a client
20:15 <@mig5> hope to release it soon
20:16 <+omega8cc> wow
20:16 <@mig5> finally i hope to do another aegir newsletter soon, it's been a while
20:16 <+omega8cc> sounds great
20:16 <@mig5> when i say 'updates stub makefiles' i mean, updated the [tag] = xxxxx for that install profile referenced in the stub makefile
20:17 <@mig5> in otherwords allows a user to manually kick off a 'Build' in jenkins and it does the whole tagged release.. standard provision-migrate etc but with proper tags etc.
20:18 <@mig5> anyways, small scrum i think. i think we also didn't have one on tuesday, too bad..
20:18 <+omega8cc> mig5: you remember Vertice idea to have makefiles subscribed via some feed and auto-generating new platforms?
20:18 <@mig5> yeah
20:18 <@mig5> that would be neat
20:19 <@mig5> you'd need something faster than cron to subscribe to it though
20:19 <@mig5> jenkins is faster atm
20:19 <@mig5> maybe, erm, node.js :) /me runs
20:20 <+omega8cc> haha, I think we need more stuff like that, to help adoption, as all those Hpowerful workflows with Jenkins etc are just over the head of 99% of the audience we could attract
20:20 <@mig5> of course
20:22 <+omega8cc> and that is my plan (and it always has been) to make it easy for people who don't really have a chance to be a power users, but want the benefits of using the Aegir stuff with their mouse only (almost)
20:24 <+omega8cc> because, you know, power users prefer command line and ci stuff etc anyway, so they will never really help in Aegir adoption, because power users are always a small percent of the audience
20:24 <@mig5> yes it's been good that you stick to your audience :)
20:24 <@mig5> the real world
20:24 <+omega8cc> both are real
20:25 <+omega8cc> just a different scale
20:27 <+omega8cc> ok
20:27 <+omega8cc> hefring: botsnack
20:27 < hefring> delicious!
20:27 <+omega8cc> scrum 

20:01 <@mig5> scrum time!
20:02 <@mig5> darthsteven: anarcat: ergonlogic
20:02 <@darthsteven> Hello!
20:02 < hefring> salut
20:03 <@mig5> i've recently started using the pack feature, as a very large client of mine will probably use it soon, so i decided to eat the dogfood and transitioned my own infrastructure onto a 5-server high-availability environment :)
20:03 <@mig5> my main issue has been http://drupal.org/node/1555398
20:03 < hefring> http://drupal.org/node/1555398 => MySQL GRANTs aren't given for multiple servers in Web Pack => Hostmaster (Aegir), Code, normal, active, 18 comments, 1 IRC mention
20:03 <@mig5> we have some funny corner cases with mysql grants
20:03 <@mig5> not actually limited to pack module, but to a case where a webserver might have multiple ip addresses in the same LAN assigned to it
20:03 <@mig5> and mysql might pick the wrong *source* IP to make the mysql connection attempt in order to fetch those to use for grants
20:04 <@mig5> i've worked around it in my case there. but anyway that's basically all i'm thinking about at the moment
20:07 <@mig5> darthsteven: can we catch up after the scrum?
20:07 <@mig5> presuming the scrum isn't done already :)
20:07 <@darthsteven> (we can)
20:08 <@darthsteven> that's great
20:08 <@darthsteven> I saw lots of comments on that issue :)
20:08 <@darthsteven> shall I go next?
20:08 <@mig5> yeah i got a bit carried away - but it was really hard to find *what* was the problem
20:08 <@mig5> sure
20:09 <@darthsteven> didn't really do too much this week
20:09 <@darthsteven> got a fix for the Drush invoke issue in Drush 5 in: http://drupal.org/node/1554092
20:09 < hefring> http://drupal.org/node/1554092 => drush_invoke_process uses 100% CPU => Drush, Base system (internal API), critical, fixed, 13 comments, 3 IRC mentions
20:10 <@darthsteven> and working with the Drush peeps to get http://drupal.org/node/1550574 sorted too
20:10 < hefring> http://drupal.org/node/1550574 => drush_invoke_process doesn't pass through alias => Drush, Base system (internal API), normal, active, 4 comments, 1 IRC mention
20:11 <@darthsteven> we should be able to support Drush 5 easily when that one is done
20:11 <@darthsteven> at the moment the 6.x-2.x branch has a workaround
20:11 <@darthsteven> but 6.x-2.x still works with Drush 5
20:11 <@darthsteven> that's it from me!
20:11 <@darthsteven> next?
20:11 <@mig5> nice!
20:12 <@mig5> i suspect that'll be it, it's only 6:12am in montreal
20:12 <@mig5> i'll wait a few min
20:20 <@mig5> ok i think that's it
20:20 <@mig5> thanks
20:22 <@darthsteven> thank you too

[05:02:37]  <@darthsteven>  anarcat, mig5, omega8cc, EclipseGc, mvc, sfyn, shrop, skwashd: scrum?
[05:02:43]  <@anarcat>  yay
[05:03:49]  <@darthsteven>  shall I go first?
[05:03:55]  <@darthsteven>  I've done not a lot
[05:03:58]  <@shrop>    Not at my computer, but will watch from mobile. Cheers!
[05:04:09]  <@darthsteven>  released 1.9 a little while ago
[05:04:23]  <@anarcat>  upgrade went through like a breeze here
[05:04:24]  <@darthsteven>  that's it from me!
[05:04:30]  <@anarcat>  alright
[05:04:31]  <@darthsteven>  next!
[05:04:43]  <@anarcat>  well, for me, thanks to omega8cc's grant, i have been able to free up more time for the project
[05:04:53]  <@anarcat>  my first focus was on urgent drush security issues
[05:05:07]  <@anarcat>  http://drupal.org/node/671906
[05:05:09]  <@hefring>  http://drupal.org/node/671906 => mysql credentials leak in drush sqlc => Drush, PM (dl, en, up ...), critical, needs review, 44 comments, 3 IRC mentions
[05:05:33]  <@anarcat>  this is mostly fixed, but i have found deep issues in the sql code and other credentials leaks that are not yet fixd
[05:05:44]  <@anarcat>  my progress can be followed here: http://drupal.org/user/1274/track
[05:06:01]  <@anarcat>  and here: http://drupal.org/user/1274/track/code
[05:06:32]  <@anarcat>  which reminds me: i have started work on a pretty dumb merge script for apache log files
[05:06:35]  <@anarcat>  http://drupal.org/project/provision-mergelog
[05:06:51]  <@anarcat>  it is designed to suck apache logs from remote servers into a single file that can then be parsed by logfile analysis software
[05:07:11]  <@anarcat>  i have done some tests with awstats, and it works well, considering awstats haven't been updated in 3 years
[05:07:17]  <@anarcat>  btw, piwik sucks for that
[05:07:21]  <@darthsteven>  cool!
[05:07:31]  <@anarcat>  while it *can* process those logfiles, it's not reliable at all and makes *ONE HIT PER LINE* on the webserver
[05:07:42]  <@anarcat>  which is a lot of fun if the piwik site is in the logfile itself :P
[05:08:03]  <@anarcat>  i have also dug my head in the SSL code again, and found quite a lot of issues
[05:08:14]  <@anarcat>  found new bugs:
[05:08:15]  <@anarcat>  http://drupal.org/node/1603722
[05:08:15]  <@hefring>  http://drupal.org/node/1603722 => deleting a site doesn't delete its SSL certificate => Hostmaster (Aegir), Code, normal, needs work, 2 comments, 1 IRC mention
[05:08:32]  <@anarcat>  and updated the existing one: http://drupal.org/node/1126640
[05:08:33]  <@hefring>  http://drupal.org/node/1126640 => move the SSL IP allocation to the frontend => Hostmaster (Aegir), Code, normal, needs work, 20 comments, 1 IRC mention
[05:08:40]  <@anarcat>  but we need to redo the SSL code, it's quite crappy right now
[05:08:52]  <@anarcat>  i am not sure we want to ditch IP management, as SNI doesn't seem quite mature enough yet
[05:08:59]  <@anarcat>  so i'd like to support both SNI and non-SNI setups
[05:09:19]  <@anarcat>  alright what else have i done
[05:09:40]  <@anarcat>  well, i guess all is left is what next:
[05:09:51]  <@anarcat>  i will work on improving migrate performance
[05:10:09]  <@anarcat>  https://drupal.org/node/1484214
[05:10:19]  <@anarcat>  i will attack https://drupal.org/node/1205458 shortly
[05:10:24]  <@anarcat>  and i'm looking for advice on how to do that
[05:10:32]  <@anarcat>  should files reside in the clients directory?
[05:11:00]  <@anarcat>  anyways, that's about it for me
[05:11:14]  <@anarcat>  i am going for a trip in sao paulo brasil between june 5th and 18th
[05:11:26]  <@anarcat>  if people want to hookup or organize a little aegir meetup there, that could be fun and useful
[05:11:32]  <@anarcat>  next up?
[05:12:35]  <@anarcat>  that was quite a monologue
[05:12:52]  <@darthsteven>  (all good stuff though)
[05:13:52]  <@darthsteven>  anyone else?
[05:14:20]  <@omega8cc> not much from me to report, other that we have now nice ssd machine for project testing etc
[05:15:12]  <@darthsteven>  indeed, thanks very much for that!
[05:15:30]  <@anarcat>  cool
[05:15:35]  <@anarcat>  who's following up on that setup?
[05:15:59]  <@darthsteven>  I am
[05:16:07]  <@anarcat>  alright
[05:16:09]  <@anarcat>  that's awesome
[05:16:18]  <@anarcat>  i noticed that ergonlogic posted something about vagrant
[05:16:21]  <@darthsteven>  should be able to get it sorted this week or next
[05:16:25]  <@anarcat>  he showed me his work, it's pretty good
[05:16:26]  <@omega8cc> ah, I have added r1soft backups there, just in case
[05:16:40]  <@darthsteven>  I'm trying to 'do it right' and set it all up using puppet
[05:18:10]  <@anarcat>  that's awesome
[05:19:32]  <@darthsteven>  we'll call that a scrum there
[05:19:34]  <@darthsteven>  oh
[05:20:11]  <@darthsteven>  actually, Drush 5 got itself a bit more sorted, and so Aegir could probably be released for Drush 5 now, if we wanted, but we'll have a better release if we wait a bit
[05:20:25]  <@darthsteven>  but we'll call it a scrum now.

We do not commit to doing all of this for 3.0, this is mostly a wishlist of what people expressed were priorities for them during the brainstorm. If people want things to move forward, they will need to submit patches or create feature branches, basically lead development on the feature you want. This page can be used to coordinate overall leadership of those issues, while pointing to the Drupal.org issue queues for the specifics.

This roadmap supersedes the previous 2.0 roadmap.

We'll start bumping items from the 2.0 roadmap over here...

1. Drupal 7 ( or 8) port of the frontend

Port frontend to Drupal 7

We were originally planning to release 1.0 with Drupal 7 support to make sure it was a "long term support" release, but this has changed - we hope to keep the release cycle short and therefore Drupal 7 was pushed back to 2.0. But it is still a target to make sure we a reliable release that will be supported for a long time.

Drupal 7 also introduces the concept of entities which could be very useful to lighten our many content types in the frontend. It could also be useful for DNS support as zonefiles could be modeled directly as entities.

This concerns of course only the port of the frontend (hostmaster.profile, eldir.theme and hosting.module), the backend already supports d7 installs and upgrades. The issue to followup is #1261030.

The Aegir maintainers are committers that have access to the code. They are responsible for specific parts of the project and are general go-to people for various things.

• cweagans - maintainer of a number of contrib modules, and contributor to several more, as well as patches to Aegir core.
• ergonlogic - Aegir Project Leader, release engineering, continuous integration testing, community site webmaster, documentation, general bugfixing, ubercart integration co-maintainer, SaaS contrib components
• helmo - hairy bugfixes and generally great contributions in the queue, maintainer for several contrib components.
• Jon Pugh - maintainer of devshop hosting/provision, provision_git, and tons of other contrib modules, submitter of many good patches
• omega8cc - nginx support Provision Sandbox, Barracuda Project

Emeritus members

These members have decided to take a less active role in the project. However, out of respect for them, and all their previous efforts for the Aegir Project (and the hope that they'll become more active again ;), they continue to have commit access.

• anarcat - debian packaging, crazy late night coding splurges, general goto guy for everything
• mig5 - testing, release engineering, migressions and general bugfixing
• Steven Jones - documentation, queueing and contexts stuff, Drupal 7 port, general bugfixing

Other contributors

Those people have given significant contributions to the project but do not yet have complete commit access.

• sfyn - ubercart integration, quota API
• Deciphered - views integration and other patches
• gboudrias - Contributor of a number of contrib modules, kplatforms and patches to Aegir core.

Sorry if your name isn't here and you have done significant contributions!! Feel free to add it or contact us if you feel you have been forgotten...

All contributors of Aegir's history can also be found on Ohloh.net's contributors page although that doesn't count patches that were sent in the Drupal.org issue queues.

Past contributors

• vertice - project founder, retired
• tbosviel - DNS support improvements
• univate - views support and batch operations
• seth.vincent - Google Summer of Code student, working on D7 port and DNS editor. Sandbox

How to join the core team

If you are interested in joining the core team, you should provide us with valuable patches or contribute to the issue queues significantly. The core team has access to all core git repositories for writing, so you will need to prove that you can provide good quality code through the issue queue. We usually notice such people and welcome them in the team directly, but you should also feel free to ask to join if you feel you are worthy.

The Aegir core team is somewhat selective about inviting co-maintainers. This is largely due to the complexity of the project, and the crucial functionality it plays for many of its users.

Below we detail the responsibilities of co-maintainership (apart from just commit rights to git), as well as what criteria we feel are important for new team members. Co-maintainership involves taking responsibility for the project's overall well-being. This includes:

• Participation in the community: issue queues, IRC, community site, etc.
• Technical involvement: bug-fixing, patch testing, new feature development and roadmap/architecture planning, release engineering, etc.
• Maintenance of project infrastructure: debian repos, community and API sites, Jenkins, etc.
• Community outreach: presentations and BoFs at Camps and Cons, blogging, screencasts, etc.

While this isn't an exhaustive list, nor are all these activities required for membership in the core team. We're looking for new team members with regular, productive activity in one or more of the above domains. This essentially boils down to two criteria:

• code/patches submissions (quality over quantity) and
• demonstrated interest in the project.

If you believe that you'd make a good addition to the core team, don't hesitate to contact any of us to discuss it.

With the recent transfer of leadership, the project's core team has decided to move towards a more democratic model, to ensure clearer structure and smoother transitions in the future. Debian is a shining example of this (in particular, the DPL), and so we will model our leadership position(s) after them.

The Aegir Project Leader (APL) is the official representative of the Aegir Project. They have two main functions, one internal and one external.

In the external function, the Project Leader represents the Aegir Project to others. This involves giving talks and presentations about Aegir and attending trade shows, as well as building good relationships with other organizations and companies.

Internally, the Project Leader manages the project and defines its vision. They should talk to other Aegir developers, especially to active contributors to Aegir core, to see how they can assist their work. A main task of the Project Leader therefore involves coordination and communication.

Obviously, we're a much smaller project than Debian, and so we're adopting a pretty minimalist organizational structure. That said, Debian has many other structures in place to ensure the ongoing health of a large community driven project. As the Aegir Project grows, we can appropriate additional tools to overcome any new challenges that arise.

Finally, the responsibilities inherent in the APL role are not exclusive to it. That is, just because it is the Project Leader's job to give presentations and coordinate our efforts, other community members should not hesitate to continue doing so themselves.

Once someone is deemed worthy of joining the core team, you (a core member) should make a proposal on the core mailing list to welcome the new developer. Subject should clearly state the proposal and give ample time for other developers to chime in. Usually all core team members should give their explicit approval as we try to reach consensus (and usually do) over proposals.

Once the member is approved on the mailing list, you should follow this checklist:

• give membership on the mailing list
• grant commit access to the core repositories (Hostmaster, Hosting, Provision and Eldir)
• grant jenkins access (simply create a user then go to the configuration page to give him the same access as others - consider also Vagrant scripts used in Jenkins and maybe the Aegir Jenkins scripts
• grant operator status on the IRC channel (/msg ChanServ flags #aegir user +*) - user needs to be registered by the member first
• grant admin access to the community site
• add the person to the core team page
• send a nice welcome email to the new member and CC the mailing list
• optionnally: announce the great news in the next release

There's an aggregated feed of all commits to the stable branches of Aegir available through yahoo pipes:

http://pipes.yahoo.com/pipes/pipe.info?_id=05014cd510f5bececc20212b20843117

Starting from April 2012, we will be holding 'office hours' twice weekly, these are opportunities when people knowledgeable about Aegir will be around to support the community.

1. When

Office hours currently take place on:

• Every Monday at 14h00 - 16h00 UTC (Convert this to my timezone)
• Every Thursday at 08h00 - 10h00 UTC (Convert this to my timezone)

2. Where

These occur via IRC on the #aegir channel, you can read about how to get on IRC on the Drupal.org IRC page. You don't need to install an IRC client on your machine to join, you can chat through your web browser.

3. What

We can discuss anything Aegir related, but ideally we'd use this time primarily for the following:

1. Helping others to contribute to the Aegir project.
2. Fixing bugs in the Aegir project.
3. Adding and clarifying documentation.

If you want to just pop along and be assigned something to do, just announce in the #aegir channel that you'd like to partake in office hours, and we'll take it from there!

Archive of release notes and changelogs

The Aegir team is very pleased to announce the official release of Aegir 3.0. This release ships with significant stability improvements, Drush 6 and 7 support, improved SSL, subdirectory multisite and nginx support and much, much more!

This release marks the deprecation of the 2.x branch. We will continue to provide security releases through the end of 2015. All Aegir users are strongly encouraged to upgrade to the 3.0 release. The upgrade has been thoroughly tested and has worked reliably for us.

Upgrading from Aegir 2.x moves Aegir from a Drupal 6 platform to a Drupal 7 one. The Debian package will migrate the front-end for you. While we have tested this with Aegir core, we strongly recommend disabling any contributed modules you may be running.

We have a very dynamic community of contrib developers, and various projects built atop Aegir. So if you were waiting for Aegir 3 to be stable, easy to install and production-ready, now is the time. The 3.x branch will be well supported as a lot of shops are running it in production already.

1. Major changes

The front-end has been ported to Drupal 7. We've also raised the minimum Drush version to 6.x, and the Debian package now installs Drush via Composer. Drush 7 is also supported.

We've added several "Golden contrib" modules to the distribution:

• Hosting Remote Import
• Hosting Site Backup Manager
• Hosting Git
• Hosting Tasks Extra

We're planning to add additional well-supported contrib modules over the course of the Aegir 3.x lifecycle. Along similar lines, we've removed hosting_platform_pathauto, as it's built-in now.

We've introduced initial Drupal 8 support, though this is still a work-in-progress. This mostly depends on Drupal 8 and Drush 8 stabilizing, before we'll be able to more fully manage Drupal 8 sites.

Aegir 3 now supports SNI for SSL.

A number of significant bug fixes and stability improvements have been incorporated. Among them, we've added locking in our task queue, and improved backup reliability significantly.

For more information, please see the slidedeck from the presentation by ergonlogic and helmo at the Aegir Summit: http://community.aegirproject.org/sites/community.aegirproject.org/files...

2. Major API changes

The API has not significantly changed, though there are a few additions. See the current API docs in the various repositories for additional details.

3. Installing and upgrading

The canonical source of installation documentation is

http://docs.aegirproject.org/en/latest/install/install/

We're in the process of converting our docs, the old version is on http://community.aegirproject.org/installing We're tracking the conversion on https://www.drupal.org/node/2534734

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.

Note that you should upgrade to the latest 2.x release (currently: 2.4) before attempting the upgrade to 3.x..

It is still imperative that you read the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade.

4. 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 :)

5. Features and improvements

In addition to the "major changes" mentioned above, the following should also be noted.

Changes since 7.x-3.0-rc1:

• #2494121: Stop servers in clusters from sync'ing back to master.
• Make the upgrade script slightly more verbose
• #2377819: Gzipping backups suppresses file permissions errors

6. Known issues

• Drupal 8 support is (Chasing HEAD) not complete. You would need Drush 8 for that.
• Drush master has an issue on Debian Wheezy (https://www.drupal.org/node/2491941)
• When upgrading from 6.x-2.x enable the betterlogin module manually.

The Aegir team is pleased to announce the first release candidate of the Aegir 3.x branch, after months of development. Development has been sometimes intermittent, but it is not over yet!

This release is tailored to make upcoming changes available to a wider audience than people ready to install from git, but also to make features more widely available and tested.

In the issue queues the central roadmap issue is: #1261030 [meta] Roadmap: Aegir 3.x (D7 port)

1. Major changes

• None, mostly small bugfixes

2. Major API changes

to be determined.

3. Installing and upgrading

The canonical source of installation documentation is

http://docs.aegirproject.org/en/latest/install.html

We're in the process of converting our docs, the old version is on 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.

Note that you should upgrade to the latest 2.x release (currently: 2.4) before attempting the upgrade to 3.x..

It is still imperative that you read the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade.

4. 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 :)

5. Features and improvements

In addition to the "major changes" mentioned above, the following should also be noted.

Changes to hostmaster since 7.x-3.0-beta2:

• #2522048 by gboudrias: VBO security update 3.3

Changes to provision since 7.x-3.0-beta2:

• #2530904 by PascalAnimateur: Unknown package version in Drupal 7
• #2530904 by PascalAnimateur, ybabel: Package version always set to Unknown
• #2511772 by danwonac - Nginx: Restore support for legacy rewrites non-clean URLs
• #2497091 - The replacement string in the third line needs to be literal
• Clarify regex alter function API docs.
• Replace drupal_set_message by drush_log
• #2496417: Drupal 6 and PHP 5.6 (Debian Jessie)
• Match Drush 8
• Set port properly when generating temporary .my.cnf.

Changes to hosting since 7.x-3.0-beta2:

• #2507089 by gboudrias: Dependency on overlay?
• #2446749 by Jon Pugh: Improve hosting task drush hooks and status update

6. Known issues

• Drupal 8 support is (Chasing HEAD) not complete.
• Drush master has an issue on Debian Wheezy (https://www.drupal.org/node/2491941)

The Aegir team is pleased to announce the forth preview release (beta) of the Aegir 3.x branch, after months of development. Development has been sometimes intermittent, but it is not over yet!

This release is tailored to make upcoming changes available to a wider audience than people ready to install from git, but also to make features more widely available and tested. More beta releases will be published when there are substantial changes.

In the issue queues the central roadmap issue is: #1261030 [meta] Roadmap: Aegir 3.x (D7 port)

1. Major changes

• Fixed a security issue in the protection of the files directory for multi-site.
• Improved SSL support
• Both Drush stable (6.6.0) and 7.x (the master branch) are supported.

2. Major API changes

to be determined.

3. Installing and upgrading

The canonical source of installation documentation is

http://docs.aegirproject.org/en/latest/install.html

We're in the process of converting our docs, the old version is on 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.

Note that you should upgrade to the latest 2.x release (currently: 2.4) before attempting the upgrade to 3.x..

It is still imperative that you read the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade.

4. 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 :)

5. Features and improvements

In addition to the "major changes" mentioned above, the following should also be noted.

Changes ho hostmaster since 7.x-3.0-beta1:

• Add hosting_remote_import to the distro.
• Update the views version in our makefile.
• Remove hosting_platform_pathauto, as it's built-in now.

Changes to provision since 7.x-3.0-beta1:

• Fix protection of files dir for multi-site
• #2036333: Remove CVS deploy code.
• Fix queue lock name.
• Fix syntax error.
• Rework bypassing of task queue lock.
• Fix lock waiting for tests.
• Use Drupal API function for lock waiting.
• #2479345: Wait for a lock on the tasks queue to be available.
• #2479885: Remove anchors and double-escaping from regexes.
• #2479885: Fix mysql filtering regex anchors.
• Add provision-tests-new-run command to start testing D8.
• #2474197: Debian package for aegir3 should depend on curl
• #2475527: Catch additional DB connection failures, and provide more meaningful error messages.
• Generate an SSL certificate for use in the default SSL vhost.
• Add NameVirtualHost for SSL, regardless of IP addresses.
• Merge branch 'dev/mysqldump-error-check' into 7.x-3.x
• Fix up docs.
• Anchor regexes, cleanup docs.
• Split regexes into helper function with alter hook and static caching, and add docs for new hook.
• Clarify docs.
• Split mysqldump filtering into a helper function.
• Dedupe generating descriptors fro proc_open().
• Document new method and fix typos.
• Dedupe temporary mysql config generation.
• Fix up some syntax errors.
• fix comment typo
• handle mysqldump errors again
• #2471805: Add hook_provision_deploy_options_alter() invocations to migrate and restore, and document it in te API.
• #2471805: Add hook to allow injecting options into clone deploy tasks.
• Rename incorrect verify method.
• #2468203: provision-save: default profile from 'default' to 'standard'
• upgrade.sh: move variables to the top
• upgrade.sh: move function definition
• ssue #2460023: Fix existing symlink problem in Ubuntu/Debian upgrades.
• Cleanup upgrade.sh script
• Rename DRUSH_VERSION variable to separate current and new
• Fix Drush version in upgrade script

Changes to hosting since 7.x-3.0-beta1:

• escape < and >
• D7 API update
• code style updates
• Form API update
• Allow sites to be installed when SSL is enabled, but no servers provide the SSL service yet.
• Fix typo in table class.
• Redirect to home page after deleting a Hosting object.
• Allow re-use of deleted servers' hostnames.
• Don't block tasks queue when running queue daemon.
• Release locks in other shotdown contexts.
• Move lock acquisition and release outside of main queue daemon loop.
• Fix queue lock name.
• #2479345: Refactor queue locking to use Drupal API.
• #2464949: Avoid needless saving of related nodes on context_import
• Fix codestyle
• Log which task starts processing
• Pass less optionss ... to prevent Unknown option errors.
• Stop overwriting node titles when importing context data.
• Fix platform migrate confirmation form status.
• #2479001 by mwisner: Fix platform migrate task form does not rebuild correctly
• Fix platform migrate form checks for sites and available target platforms.
• Provide a default platform.
• Allow platform paths to have slashes.
• #2469179: Remove duplicate call to hosting_ssl_filter_key, its in hosting_ssl_nodeapi_site_validate
• #2469179: Improve saving a new SSL key
• #2475455: Document the place for am intermediate certificate.
• Try again to keep warning/error jump links within overlay.
• Keep warning/error jump links within overlay.
• #2175619: Add links to first warning or error in task log.
• Fix check for a platform's path already existing.
• #2474801: Fix task cancellation.
• Syntax fix.
• Add global option to always, never or prompt to delete site backups.
• #1397798 by chertzog, Dane Powell, et. al.: Optionally delete site backups when a site is deleted.
• #2471094: Update the site node with the database name after imports.
• Import site by calling the relevant function directly instead of invoking a sub-process, etc.
• Revert "properly import db_name after site import"
• Merge branch 'dev/hosting-import-dbname' into 7.x-3.x
• partly revert e3bb221: properly save drush output
• properly import db_name after site import
• code cleanup
• Improve ssl description
• #2453807: Convert clients list block to views
• Merge backend output.
• #2470297: Run 'hosting-import' after 'provision-import' on 'import' tasks.
• Revert portion of last commit, included by mistake. It will be part of the nest commit.
• Show backend output that was being lost.
• #2470297: Stop overwriting context prior to import.
• Set platform path automatically, based on title.
• Move site SSL fields into fieldset.
• Merge remote-tracking branch 'origin/dev-sni' into 7.x-3.x
• #2069431: Indicate next steps after enabling the SSL feature.
• Fix backup-delete form validation warnings.
• Fix restore form validation warning.
• #2460937: Fix backup deletion.
• Add some checks to backup delete validation.
• only warn about SNI, do not disable SSL, when IP allocation fails
• do not set IP address if none provided, this should permit SNI, in the frontend at least

6. Known issues

• Drupal 8 support is (Chasing HEAD) not complete.
• Drush master has an issue on Debian Wheezy (https://www.drupal.org/node/2491941)

The Aegir team is proud to announce the forth release in the stable 2.x release branch!

This maintenance release ships with a security fix for Apache installations. Everyone is encouraged to upgrade. Re-verify is required for all sites (Views bulk operations makes this easy)

Also, worth noting is the simultaneous release of our second beta for Aegir 3. Debian packages are now being provided for Aegir 3, so trying it out is easier than ever!

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 at:

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.

N.B. Issue #2146977: Broken backward compatibility with IP based vhosts may affect those upgrading from 1.x. It appears that running 'verify' tasks on all sites should resolve the issue.

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 :)

3. Known issues

Being really open about our project, we have never hidden the fact that some things, sometimes, do not work in Aegir. Our issue trackers are public, and we've made it a point of honor not only to document clearly what is wrong in our releases as soon as we find out about it, but also to reroll new releases when we fix it.

That being said, 2.4 still has a number of issues and design flaws. This is the list of all issues marked "major" in the queue right now. Most issues are now likely to be fixed in the 3.x development branch, and unlikely to be backported unless considered critical.

As mentioned in the previous section, Issue #2146977: Broken backward compatibility with IP based vhosts is still listed as a 'critical' issue against the 2.x branch. However, it should only affect those upgrading from 1.x, and has a fairly simple work-around. If you come across this behaviour during your upgrade, please post a comment to the issue, so we can confirm that it still exists.

4. Features

5. Bug fixes

• Just the mentioned security fix

The Aegir team is proud to announce the twelfth (and final!) release in the now deprecated 1.x release branch! This release was necessary to cover the new Modalframe security release that made 1.11 uninstallable. Everyone is encouraged to upgrade to the latest 2.x release.

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 releases prior to 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or 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!

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 :)

3. Known issues

The modalframe upgrade broke popups, but the content is visible so it is a minor regression. Upgrade to 2.x to get a real fix.

Otherwise the same as the 1.11 release.

4. Features

• Apache 2.4 is now supported in the 1.x branch, see #2153929 and #2155445 (7 weeks ago)

5. Security fixes

• modal frame was updated to cover for SA-CONTRIB-2014-012 (#2191827)

6. Bug fixes

• the jQuery download URL was fixed

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

The Aegir team is pleased to announce the first preview release (alpha) of the Aegir 3.x branch, after months of development. We have been pretty busy with the maintenance of the 2.x branch, so development has been sometimes intermittent, but it is not over yet!

This release is only a first of a series of alpha releases that are tailored to make upcoming changes available to a wider audience than people ready to install from git, but also to make features more widely available and tested. More alpha releases will be published when there are substantial changes.

In the issue queues the central roadmap issue is: #1261030 [meta] Roadmap: Aegir 3.x (D7 port)

1. Major changes

• Frontend ported to Drupal 7
• Raised minimum Drush version to 6.x
  • Drush 7.x is supported, but that's a matter of chasing head.

2. Major API changes

to be determined.

3. 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.

Note that you should upgrade to the latest 1.x release (currently: 1.9) before attempting the upgrade to 2.x. This is especially important if you are running a pre-1.0 release (poor you!).

It is still imperative that you read the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade.

4. 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 :)

5. Features and improvements

In addition to the "major changes" mentioned above, the following should also be noted.

6. Bugfixes

This is a non-exhaustive list.

7. Known issues

• The devel module is listed as dependancy for the hostmaster install profile, but is not included in the drupal.org build.

The Aegir team is pleased to announce the second preview release (alpha) of the Aegir 3.x branch, after months of development. Development has been sometimes intermittent, but it is not over yet!

This release is tailored to make upcoming changes available to a wider audience than people ready to install from git, but also to make features more widely available and tested. More alpha releases will be published when there are substantial changes.

In the issue queues the central roadmap issue is: #1261030 [meta] Roadmap: Aegir 3.x (D7 port)

1. Major changes

• Improved Drupal 8 support

2. Major API changes

to be determined.

3. 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.

Note that you should upgrade to the latest 2.x release (currently: 2.1) before attempting the upgrade to 3.x..

It is still imperative that you read the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade.

4. 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 :)

5. Features and improvements

In addition to the "major changes" mentioned above, the following should also be noted.

6. Bugfixes

This is a non-exhaustive list.

Changes since 7.x-3.0-alpha1:

• Improve readability of message
• #2348173 by helmo: Remove unused vars causing trouble
• #2372653 by helmo: Add --no-autocommit when dumping MySQL tables
• typo
• Fix platform name in demo content
• don't make the example module warn so much
• propagate example_field properly to the backend
• Improve debug messages in Config classes.
• Nginx: Helper locations to avoid 404 on legacy images paths (subdir only)
• Nginx: Fix spacing
• Nginx: Add missing variables in subdirectory config template.
• don't allow d() to run before drush is fully initialized
• clarify little debugging markers
• silence the last warning, it's actually not one
• add debugging: when no service type is specified from the frontend, yell a warning
• remove dead code: $base_dir is not used anywhere in that function
• Split arrays and hooks to alter chmod and chgrp file operations.
• Add server data example module, which doesn't currently work.
• Add post_verify hook for site_data module.
• Remove legacy drush load for site data example module.
• revert previous commit, it's too noisy
• clarify traces in site_data module
• Nginx: Add the fix for known problem with files/imagecache in legacy D6 sites (again).
• Remove openatrium2 from testcase, build fails too often on external issues
• Update openatrium2 test platform to new tag
• Rename makefiles to .make extension
• #2373835 by helmo | realityloop: 3.x doesn't currently install.
• Nginx: Fail early if any required db credentials are empty, to never create broken vhost.
• Nginx: Block semalt botnet (extended boa mode only)
• Nginx: Batch merge updates from 6.x configuration (2)
• Nginx: Batch merge from 6.x configuration.
• Correct package name in changelog
• Update debian package info to have aegir3 in the name
• Fix branch name for 7.x-3.x in debian git-buildpackage
• #2358795: Adding a "$force" parameter to setProperty() to allow overwriting of default context properties.
• #2358795 Adding a provision-save to provision_verify command.
• #2361729 by joestewart: Fixed D8 Platform verify doesn't add module version to package.
• #2365171 by joestewart: Fixed D8 Contrib profiles in /profiles undetected.
• #2362707 by joestewart: D8: update private and temporary paths after cloning
• allow overrides to the site-specific drushrc.php file
• #2163979 - Check if field_info_field_map() is available to not break support for old D7 versions.
• #1995506 by Jon Pugh: Added Implement "--profile" option for "drush hostmaster-install".
• Add API doc for new hook.
• Allow altering the list of directories to recurse into on site/platform creation.
• Removed a bashism
• #2348879 by Deciphered, helmo: Fixed Welcome Mail - url() deprecated.
• Remove a trailing space char
• refactor
• Improve error handling, better message and fail earlier.
• #2300537 by helmo | ergonlogic: Added Merge Provision extensions into Hosting modules.
• Make sure that db_port is never empty and defaults to 3306.
• Add drupal 8 to provision-demo-content
• #2346903 by helmo: Added Always disable allow_authorize_operations.
• #2311005 by Deciphered, clemens.tolboom: Fixed D8 Site install fails on undefined indexes.
• #2306055 by Deciphered, realityloop, helmo, clemens.tolboom: Fixed Platform verify fails for Drupal 8 under Aegir 3.x.
• #2346967 by Deciphered: Fixed Onetime login link broken.
• Pin test makefile of openatrium to stable version, to avoid build problems.

7. Known issues

• Drupal 8 support is (Chasing HEAD) not complete.
• Upgrading a hosted site from D6 to D7 has complications with Drush > 7.0.0-alpha6 issue

The Aegir team is pleased to announce the third preview release (beta) of the Aegir 3.x branch, after months of development. Development has been sometimes intermittent, but it is not over yet!

This release is tailored to make upcoming changes available to a wider audience than people ready to install from git, but also to make features more widely available and tested. More alpha releases will be published when there are substantial changes.

In the issue queues the central roadmap issue is: #1261030 [meta] Roadmap: Aegir 3.x (D7 port)

1. Major changes

• Improved Drupal 8 support
• Both Drush stable (6.5.0) and 7.x (the master branch) are supported.

2. Major API changes

to be determined.

3. Installing and upgrading

The canonical source of installation documentation is

http://docs.aegirproject.org/en/latest/install.html

We're in the process of converting our docs, the old version is on 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.

Note that you should upgrade to the latest 2.x release (currently: 2.3) before attempting the upgrade to 3.x..

It is still imperative that you read the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade.

4. 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 :)

5. Features and improvements

In addition to the "major changes" mentioned above, the following should also be noted.

Changes to hostmaster since 7.x-3.0-alpha2:

• #2450683 by cweagans: Enable r4032login in the default hostmaster install
• Update the ctools version in our makefile.
• Update the entity API version in our makefile.
• #2421341 by clemens.tolboom, helmo: Add default permissions on install
• Regular contrib updates for admin_menu, betterlogin and ctools
• Update the views version in our makefile.
• #2393567: Betterlogin's anon redirect causes issues with services

Changes to hosting since 7.x-3.0-alpha2:

• #2448855 by Pol: Makefile field not saved when importing platforms
• log task processing in drupal
• #2393579: Signup feature cleanup
• #2407885: refactor SSL forms - hide other SSL fields when not enabled.
• SSL code cleanup
• Rename hosting_ip_delete to _hosting_ip_delete to avoid looking like hook_delete
• Rename hosting_ip_load to _hosting_ip_load to avoid looking like hook_load
• Rename hosting_ip_validate to _hosting_ip_validate to avoid looking like hook_validate
• Rename hosting_ip_save to _hosting_ip_save to avoid looking like hook_save
• Rename hosting_ip_view to _hosting_ip_view to avoid looking like hook_view
• Fix typo in variable name
• Allow numbers in Hosting feature names.
• Fix logic flaw
• Fix remaining boolean in access grants.
• #2410603: Fix default value
• #2410603: Working copy isn't currently working
• Remove duplicate reaction to enabling modules.
• Allow scripts to skip automatic verify tasks when enabling modules by passing '--no-verify'.
• Hook into module being disabled
• node_revisions table name changed to node_revision with D7
• #2430807 by clemens.tolboom, helmo: Roles order is reversed to advised order.
• Fix default permissions for optional submodules
• Fix typo in permission name
• #2432397: Add static cache to hook_node_grants
• #2430809 by clemens.tolboom: Notice: Undefined variable: grants
• Do not add validation when the form elements are not added
• #2430103 by clemens.tolboom: hosting_client: Strict warning: Only variables should be passed by reference
• Update db placeholders
• #2410209: Use bigint to store backup size
• Log which drush task hooks we're invoking.
• #2210813 by ergonlogic, realityloop: Follow-up from D7 DBTNG changes
• Rename constant MAX_GROUP_LENGTH to HOSTING_CLIENT_MAX_GROUP_LENGTH
• #2408365 by clemens.tolboom: Strict warning when adding new client

Changes to provision since 7.x-3.0-alpha2:

• #2457359: Stop overriding Nginx SSL settings
• #2396299 by ergonlogic: Stop comparing platform package versions when said package is installed in the site
• Merge branch '7.x-3.x' of git.drupal.org:project/provision into 7.x-3.x
• Nginx: Stop the POST flood to /autodiscover/autodiscover.xml generated by MS Office/Outlook
• Debian: improve setting directory permissions.
• #2193427 by helmo: Remove Debian package requirement for Drush
• Make php5-gd a dependency of the aegir3-hostmaster package, as its required to install core
• Log site installation exception.
• Update absolute URLs to files for sites cloned/migrated/renamed
• Nginx: Use dummy db fastcgi_param placeholders if any of them is empty
• #2350695 by omega8cc, helmo: Profile is registered twice, also as a module, which causes warning
• Nginx: Remove webform keyword from regex locations - fixes #599
• Remove Drupal 8 specific stuff from D7/D6 template.
• Both maintenance_mode and clean_url are ignored in Drupal 8
• Fix for custom cpuinfo logic.
• Nginx: Sync configuration improvements.
• Remove docs for non-existing option
• Add the working-copy option to hostmaster-migrate, similar to hostmaster-install
• hostmaster-resume was renamed to hosting-resume
• #2421543 by notzach: Changing how Apache ServerAliases are defined
• Drupal 8 requires trusted_host_patterns defined in settings.php
• Drupal 8 requires container_yamls defined
• Nginx: Use safe fallback for mysteriously empty $db_port
• Nginx: Use reliable source for db_port to write in the vhost
• #2409085 by clemens.tolboom: Use mutatable interface in install_8.inc
• #2387953: Remove drush-make from Debian suggest line.
• #2276557 by zxaos, bgm: allow aegir2-provision package to accept mariadb or mysql
• Nginx: Fix for D8-specific /cron/ location caching (extended mode only).
• Nginx: Fix for D8-specific /cron/ location regex.
• Update deploy_8.inc to sync it with improvements in deploy_7.inc
• Set files paths on D8 install to avoid using system default /tmp if path.temporary is not defined.
• Nginx: Sync headers configuration in the extended mode.
• Do not copy CDN aliases to the cloned site --CDN vhost.
• Detect and update default D8 site name, if needed.
• #2362703 by joestewart - import_8 ineffective.
• Sync with 6.x workaround for systems with access to /data/all/cpuinfo instead of /proc/cpuinfo
• Sync subdirectory support.
• Force clean URLs for Drupal 8.
• The /login suffix is no longer supported in Drupal 8 and results with confusing 404 error.
• Avoid broken install on D8 core where sites/all doesn't exist by default.
• #2183323 - Remove all remnants of $GLOBALS['conf']
• Fix for removed drupal_mail() which breaks Drupal 8 head install if used.
• Restore missing !edit_uri with hardcoded standard URI.
• Nginx: Drupal 8 with clean urls enabled should use /cron/ URI.
• Nginx: Sync config templates.
• Add missing code for subdirectory mode detection and support.
• Detect if the platform stays the same only when site name changes.
• Use $new_name instead of $new_uri to avoid confusion.
• Compare $new_uri with d()->name and not d()->uri in the Site Rename Check.

6. Known issues

• Drupal 8 support is (Chasing HEAD) not complete.
• The upgrade.sh.txt in provision still had Drush 5.10.0, be sure to change it to 6.5.0 before using that script.
• The upgrade code in the Debian package could fail on an exsiting /usr/local/bin/drush file, this has been fixed in https://www.drupal.org/node/2460023

This section documents all the older releases in the 2.x release cycle.

The Aegir team is proud to announce the second release in the stable 2.x release branch!

But first, here's a word from Antoine Beaupré:

This latest release of the Aegir project will be the last one for me as a release manager, as I will be stepping down from the leadership position I have filled in the 7 years of involvement in this amazing project. I will continue to contribute to the project, to a lesser extent. I will remain available, through Koumbit, to provide high-level consulting work for Aegir. We can also now welcome Praxis Labs Coop as a new consulting partner of the Aegir project. Praxis will help to finance ongoing Aegir development by subsidizing part of my salary, in a similar fashion to how Omega8.cc had in the past.

Working with the Aegir project was a huge challenge, both from a technical perspective, but also from a human standpoint, as it is a large and complex project that may seem daunting for new users. But with regular releases and continuous support in the issue queue, I think we have been able to foster a great community of contributors that goes beyond what a single person can do, as Adrian proved when he left the project with the 1.0 release in 2011. Christopher (ergonlogic) and other contributors have shown they are in a good position to take over that leadership role, and will do so from now on.

Now it is my turn to move on, and I am quite proud of what I leave behind. This project allowed me to travel around the world, meet incredible people and learn a lot about hosting and provisioning. It is however time for me to move on. I have been involved with the Drupal community for over 13 years, and things, to put it lightly, have changed. PHP is attempting to become a real programming language, something that I didn't believe could or should happen, and I wish to move on to other paradigms. Python and Haskell are waiting for me around this turn in the road, and even Perl and shell scripting look awesome in comparison to those dreaded PHP years. Besides, since Aegir started, lots of configuration management systems have popped up that we can leverage to host way more than PHP and Drupal: Docker, Chef, Puppet hold lots of promise for those of us who dare to get out of the NIH syndrome. Hopefully, that energy will be reusable in the Aegir project as we head towards Aegir 4!

And so, thank you, Antoine, for all your great contributions as leader of the Aegir project! You have been an inspiration to many of us, and have provided superbly effective technical leadership.

This release ships with support for Apache 2.4, along with updates to Drupal core and ModalframeAPI. A number of bug-fixes are included affecting deployment of Drupal 7 sites, aliases with sub-directory installs, backups, among other things. See below for the full lists of new features and bug fixes. Everyone is encouraged to upgrade.

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 at:

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 releases prior to 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or 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. Noone likes a nasty surprise!

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 :)

3. Known issues

Being really open about our project, we have never hidden the fact that some things, sometimes, do not work in Aegir. Our issue trackers are public, and we've made it a point of honor not only to document clearly what is wrong in our releases as soon as we find out about it, but also to reroll new releases when we fix it.

That being said, 2.1 still has a number of issues and design flaws. This is the list of all issues marked "major" in the queue right now. Most issues are now likely to be fixed in the 3.x development branch, and unlikely to be backported unless considered critical.

• hosting-queued doesn't get properly re-enabled on upgrades, see #2114675 for a workaround.
• previous Debian packages may remove the aegir.conf symlink before being upgraded. this is fixed in 2.0 but will occur (it's inevitable) during upgrades from 1.x releases. details and simple workaround in #2121263

4. Features

• Apache 2.4 is now supported in the 1.x and 2.x branches, see #2153929 and #2155445
• updated core to Drupal 6.31
• #2191827 by Jon Pugh: Update modalframe

5. Bug fixes

• #2157785 by helmo: Deploy_7 code lacks functionality from D6 code
• #2169025 by gboudrias: Fix non-gzipped backups can't be restored
• #2213387 by Chris Moates: Fix alias handling when using subdirs support
• Cleanup some file permissions from 755 to 644
• #2213787 by SocialNicheGuru, helmo: Undefined property: stdClass::$ssl_key_new hosting_ssl.nodeapi.inc:252
• Fixed reference in comment and cleanup notices
• #2171075 by helmo: Fix hostmaster-resume command options. (3 months ago)
• #2189687 Redirect to site-alias not working

The Aegir team is very pleased to announce the official release of Aegir 2.0.0. This long-awaited release ships with significant stability improvements, Drush 5 and 6 support, subdirectory multisite support, improved nginx support, native views and much, much more! We unfortunately had to drop support for Drupal 5, as Drush 5 and 6 dropped support for this unsupported Drupal release.

This release deprecates the 1.x branch, marking the 1.11 release as the last one of the 1.x branch. All Aegir users are strongly encouraged to upgrade to the 2.0 release. The upgrade has been thoroughly tested and works fairly reliably, except some documented minor issues.

We have a very dynamic community of contrib developers, and various projects built atop Aegir. So if you were waiting for Aegir 2 to be stable, easy to install, production-ready, now is the time. The 2.x branch will be well supported as a lot of shops are running it in production already.

1. Major changes in this release

Since th 1.0 stable release (1.0) in April 2011, we've done an incredible amount of work. The code size nearly doubled as did the development team and user base. We have accomplished a significant number of the release goals we set for 2.0, but not all. Here is a broad breakdown of the most important improvements between the 1.11 and 2.0 releases:

• Subdirectory multisite support
  • you can now have different sites in example.com/foo and example.com/bar, a great feature if you do not control DNS, as well as for local development!
• SSL improvements
  • IP allocation improvement: addresses can be changed, added and removed more easily, and are managed from the front-end now.
  • SSL certificate generation now has saner defaults (e.g. 2048bits)
  • better error handling
• Drush 5 & 6 support
  • includes better support for archive-dump command
  • means we also drop the dependency on drush make 2.3, now included in Drush 5
  • support for Drush 4 has been dropped, the minimum version is now 5.5, but Drush 6 or 5.10+ is recommended.
• Packaging improvements and changes
  • Nginx support in the Debian package
  • now a "native" debian package
  • package name changed: it is now aegir2, aegir2-provision, etc, to avoid overwriting the previous package - note that aegir 1 and 2 can not be installed in parallel
  • hosting and eldir now split back in their own projects on dripal.org
  • using Drupal.org packaging tools to provide a full tarball for the whole frontend, speeding up installs significantly
• Nginx improvements:
  • fixed support for nginx 1.3 and newer
  • better defaults for caching
  • SSL and Nginx are now officially supported (not marked as "experimental")
• New modules:
  • the hosting-queue-runner module is now merged into core as hosting-queued
  • "pack" module, designed as a lightweight replacement to the "cluster" module, now available as an experimental extension
• Hosting-queued improvements
  • run with a lower priority ("niced")
  • improved portability and reliability of startup script
  • enabled by default in the Debian package
  • improved stability
• Code refactoring and improvements:
  • now using the Symphony autoloading code
  • fix coding style in a lot of source files
  • improved builtin test suite
• Frontend improvements:
  • all custom displays ported to Views and VBO
  • nicer frontpage
  • new and improved roles with more useful default permission sets
• Documentation improvements:
  • Our documentation initiative to better document the Hostmaster API has progressed nicely
  • we'll be launching an updated version of our API site (along the lines of api.drupal.org) shortly, to ease exploring the code-base of the Aegir Project, see this issue.

For a more detailed list of new functionalities, bugfixes and API changes, see below.

Some goals of the original 2.0 roadmap have not been accomplished, namely:

• modular backup, platform and queuing systems - although work has started on Wordpress support, and an overhaul of the Aegir architecture is considered for 4.0, which will affect queuing systems (see below)
• DNS, PostgreSQL and statistics efforts have mostly stalled
• clone and migrate optimizations still have to be completed
• completely automatic upgrades have not been implemented, although the Debian package upgrades are working generally well
• the release was about 2 months late from the october 31st estimate

1.1. 2.x branch maintenance policy

With the 2.0 release, the Aegir project wished to adopt the growing standard of Semantic Versioning. Unfortunately, the tools on Drupal.org do not allow 3-digits version numbers in contrib, something of a blocker to allow us to use that great numbering scheme. So we will stick to our previous scheme for now, but we'll consider a switch to semver for 3.0.0.

No API change will be done in the 2.x branch. All core development will now happen on the 3.x branch, which shifts the focus of development to the port of the frontend to Drupal 7 (almost complete).

Note that the 2.x API has already been frozen for some time, since the first release candidate, to be more precise. Major changes to 2.x will not be committed unless they are first tested in 3.x and merged back. However, we wish the 2.x branch to be relatively short-lived, and it is more likely that major changes will not be backported from 3.x unless absolutely necessary for users needing a Drupal 6 Aegir frontend.

The 1.x branch is now deprecated and the 1.11 release will be the last release of that venerable branch, unless we need another release to fix the upgrade path to the 2.x branch. This is considered very unlikely. Security fixes or critical issues will therefore not be backported to the 1.x branch.

1.2. The future

While we're very proud of what we've accomplished in Aegir 2.0, we've also been working in parallel to port Aegir to Drupal 7. Aegir 3.0 has already begun as a fairly straight-forward port. As such, we'll be releasing our first alpha of Aegir 3 shortly. We would like to have a stable Aegir 3.0 release before the release of Drupal 8, to allow for users to transition as Drupal 6 enters its end-of-life phase.

The reason for the change to semantic versioning is that we've been discussing a full re-write of Aegir for some time, and would like to do so with Aegir 4. The changes are likely to be fairly drastic, and so we want to be able to keep moving Aegir 3 forward in the mean time. By moving to Drupal 7, we expect to have bought ourselves 2+ years of breathing room within which to accomplish this re-architecture and the semantic versioning system allows us to integrate major changes in the 3.x branch progressively.

When the Aegir project started (back in 2008), the free software options for systems management software were very limited. As a result, we wrote our own code to do things like deploying code, writing configuration files, starting and stopping services, and so forth. Now, as 2014 begins, there are a wealth of tools that perform these functions (e.g. Puppet and Chef, but also Openshift, Docker, etc), each with their own communities supporting them. We are exploring how we might be able to leverage these tools, rather than maintaining our own partial implementations, that will never likely be as robust as these more specialized projects.

We feel that the time is opportune since Drupal 8 will require significant re-writing of the front-end components. In addition, re-writing the backend so completely will allow us to seriously consider moving to a programming language other than PHP; one that would be better suited to the project's long-term goals, such as Python or Ruby.

2. 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.

For users coming from the 2.0 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!

Note that you should upgrade to the latest 1.x release (currently: 1.9) before attempting the upgrade to 2.x. This is especially important if you are running a pre-1.0 release (poor you!).

2.1. 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 :)

2.2. Known issues

Being really open about our project, we have never hidden the fact that some things, sometimes, do not work in Aegir. Our issue trackers are public, and we've made it a point of honor not only to document clearly what is wrong in our releases as soon as we find out about it, but also to reroll new releases when we fix it.

That being said, 2.0 still has a number of issues and design flaws. This is the list of all issues marked "major" in the queue right now. Most issues are now likely to be fixed in the 3.x development branch, and unlikely to be backported unless considered critical.

• hosting-queued doesn't get properly re-enabled on upgrades, see #2114675 for a workaround.
• Ubuntu saucy has some changes in apache config wich breaks Aegir #2155705
• previous Debian packages may remove the aegir.conf symlink before being upgraded. this is fixed in 2.0 but will occur (it's inevitable) during upgrade. details and simple workaround in #2121263

3. Complete list of changes

Her is the complete list of changes, since the 1.x branch, some of which were already mentioned in previous release notes for alpha/beta/rc releases.

3.1. API changes

Those changes are, as usual, more explicitly documented in the upgrade path documentation.

• hosting-task now needs a --force argument to run a non-queued task
• the '--force' option also allows running tasks that appear to be running in the queue
• functions that were deprecated in 1.x are now removed
• the email and client_email database fields are now removed from client and site node types
• numerous changes to the IP allocation and SSL management code
• deprecate hosting_ip_delete_revision(), dupe of hosting_ip_delete() now that revisions are gone (8 weeks ago)
• remove deprecated DEBUG flag in debian package
• #1785624: Some Drupal API changes in D7 (and D8) are not used/respected properly
• #1945950: Rename provision_drupal_sync_site_back()
• #1083366: Make the spokes authoritative for files/ and private/ directories
• #1812338: Refactor sync back
• a new control file has been introduced in /etc/nginx/basic_nginx.conf to force the nginx configuration to be the "simpler" one (see #1635596)
• #1987026: Move generated platform drushrc.php to sites/all/drush
• Multiple files can be managed in a single context now (see issue #2000038, issue #1784108)
• #1034520: Cleanup package instances when deleting sites and platforms.
• #1830220: Drop support for Drupal 5.
• #1975086: Move log parsing and status updates to seperate functions and call them from a shutdown function.
• Pass the entity type when we're sync'ing package instances.
• Save the platform field when creating a package instance record.
• Move to individual operation callbacks for VBO tasks.
• #2022849: Record disable and delete backups in the database.
• #2031491: Rename SSL permission to be more descriptive.
• Fix node grants so that proper permissions are respected on all Aegir node types.
• Add 'administer' permissions for platforms and servers, and allow platforms to be viewed.
• #1283738: Allow other commands to add or alter the directories to be created.
• remove version pinning in hostmaster, our release process now again needs to modify only one makefile (#2002114)
• #1986928: Provide 2.x upgrade guidance for services
• #2099889: More hosting_features checks in _drush_load hooks?
• #1882708: Unused 'release_id' field in 'hosting_platform'
• #2012508: hosting_context_name returns '@' if node not found
• #1283738: Add new hook provision_drupal_create_directories in _provision_drupal_create_directories
• There is now a registry in the backend of the features enabled in the front-end (in /var/aegir/.drush/drushrc.php) which allows backend components to better determine if they should act
• If /var/aegir is a symlink, it will be destroyed by the debian package, make sure the Aegir $HOME is properly set to work around that, see issue #2118857

3.2. New features

In addition to the "major changes" mentioned above, the following should also be noted.

• #1830994: Login directly via 'login' link
• #1853588: Sort Install profiles on Site add form
• #709862: Allow drush modules to add to apache vhost config template
• #1861896: Make $type argument of function hosting_available_tasks() optional.
• #1843198: Add Content top and bottom to Eldir.
• #1826074: Add tests to ensure site directories are migrated
• #1464220: Support alternative 'Hostmaster' profiles
• #610040: Add X links on listing pages
• #710834: notify clients on site migrations
• #1260066: Allow use of the working copy option when creating a platform
• #1047992: exportable backups
• #1189556: Pull the queue runner into Aegir 2
• #1408410: Add microcaching to Nginx config by default
• #1138104: Tiny module to automatically fill in platform publish path based on title
• #1929372: Flag tasks with logged warnings
• #1515416: On a package page, show table listing sites and platforms using the package
• #1853620: Add db_name to site summary
• #1681904: Ability to configure a url to redirect to in site configuration.
• #1968226: manage each IP individually on the server level
• add uninstall command
• Nginx Security: BEAST attack protection and fix for PCI compliance.
• #1980136: Allow setting default profile from the front-end.
• #588728: Replace custom lists with Views and VBO for sites, platforms and packages.
• Support for installing in subdirectories (issue #705026)
• Proper homepage on startup so non-logged-in users don't see an error page, and new users have basic instructions (issue #1793740)
• SSL support for clusters should now work properly (issue #2000964)
• New roles added: 'aegir platform manager', 'aegir administrator' (issue #1403208)
• Convert list of platforms to use views (Issue #1876350)
• #600350: provide a nice "history" of ran tasks
• #1988642: Add site by platform
• #1912238: automatically build and upload aegir 2.x packages
• #585830: usability story: "How do I create a client?"
• #1212086: Platforms should be locked by default
• #1403208: Add additional roles
• #1174440: provide a way to show site's DB username/password in the frontend
• #606120: Disabled sites should be class hosting-warning, enabled but problematic sites should be hosting-error
• #905326: Improve file path changes.
• #1201174: Make UID1 username configurable.
• #1345118: Make platform access control an autocomplete form.
• #1515416: Replace listing of sites and platforms using a package with a view.
• #1975086: Add 'update status' button to tasks.
• #2005310: Add VBO operations to platforms view.
• #2006074: Enable backups via VBO.
• #2025787: Open site goto link in a new window/tab.
• #2022813: Expose backups to Views.
• #2027269: Update a task's status after all Drush operations are complete.
• #2031491: Review and update permissions for all roles.
• #2031765: Clean up VBO operations with Action Permissions.
• #2035873: Show package 'popularity' on platform package view
• #2036283: Make Aegir aware of site-specific packages.
• #2036793 Ignore hidden modules and profiles.
• #2037045: Change some log statuses to better match Drush's log styling.
• #2037965: Clean up hosting-pause.
• #2038279: Validate email during site install.
• Display all validation errors when adding a client, and limit to 20 suggestions.
• Flag rollbacks as warnings in our task logs.
• Handle package page views separately for sites and platforms.
• Update default hosting_site views to use new access plugin for blocks, and add a couple more displays for non admin listings.
• Add Views access plugin for hosting_site and hosting_package.
• Add views handler to filter packages by status.
• #2069387: Support nonstandard ports on hostmaster-install command.
• #2067617: Allow hostmaster-install to accept '--working-copy' option.
• Allow the redirect to the welcome page to be turned off.
• aegir install time reduced by about 60 seconds (on a cable uplink) by using Drupal.org distributions (#2002114)
• #2001964: Upgrade Views Bulk Operations 6.x-1.16
• #2099057: Allow _provision_drupal_create_directories to skip chmod
• #2100251: Implement post-enable hook for 'hosting_*' modules
• #2020075: Refactor subdirs to use proper Config class(es)
• #2020079: Multi-server subdirectory support
• #2096629: hook_provision_drupal_create_directories_alter by ref
• #2086009: Logo Cannot be changed / disabled
• #2069387: Support nonstandard ports on hostmaster-install command
• #2074681: Ports are hardcoded in hostmaster.profile
• #2103173: Provide an example of saving data to a site context

3.3. Bugfixes

This list only shows bug fixes since the last release candidate (RC5), since the list of all bugfixes in Aegir 2 is truly enormous. Please review the individual release notes for more details, if you are curious.

• Improve the subdir related description in the site add/edit forms, to explain the most important details clearly enough.
• Do not allow duplicate subdir aliases - use hosting_alias_allow_domain() in hosting_alias_validate_subdir() directly.
• Update the inline how-to for sites in subdirs.
• #2020089 by ergonlogic - Allow example.com and example.com/foo domains (Hosting)
• #2151475 by helmo: Extra comment.
• #2151371 by helmo: Allow custom platform tasks.
• security fix: SA-CORE-2013-003, fix files/ protection
• #1220062 fix mild security issue with login-reset links.
• fix SSL certificate garbage collection, it was simply not working
• reformat complex query to be more readable
• also free SSL certificate when SSL is disabled on a site
• check only client nodes for duplicates, closes #2123355
• #2119101: Fix tasks are not sorted properly.
• don't verify deleted sites, fixes #2119111
• properly populate the SSL cert / IP association map
• properly count the aegir hosting aliases, fixes #2118917
• Fix malformed @defgroup.
• #2085077 by chertzog | ergonlogic: Fixed Invalid argument supplied for foreach() hosting.ip.inc:39.
• #2126895 by helmo: Upgrade.sh not compatible with Drush 6.
• #2020089 by ergonlogic - Allow example.com and example.com/foo domains (improved to fix a few dangerous errors) plus comments.
• Nginx: Use text/xml mime type for .xml URLs to restore defaults.
• Fix the check for parent site existence - we should look for drush alias file and not a vhost (which can be dummy subdir vhost).
• Nginx: Fix aliases in redirects on the fly.
• Nginx: Convert subdir alias name properly when used as server_name in redirection.
• #2020089 by ergonlogic - Allow example.com and example.com/foo domains (Apache)
• Nginx: Redirect to working homepage for subdir based site.
• #2100181 by ergonlogic - Symlink missing for D6 subdir sites.
• #2146711 by helmo: PHP 5.3 compatible (Nginx).
• #2038891 by drastik: add missing --client-email option
• #2020091 by ergonlogic - Support subdirs with Nginx.
• fix redirection for non-ssl hosts, issue #2148671 by logaritmisk
• #2157785 by helmo: Remove unused variables, these get written to the site's settings.php anyway.
• #2157783 by helmo: Deploy_7 code has an unused old_uri.
• don't go around destroying apache configs on upgrades or removal
• get the aegir home directory dynamically
• rename VARLIB variable to AEGIRHOME for clarity
• fix drush dependency: we need 5.10 to treat hostmaster as core in drush make
• Further fixes for strict options checking in Drush 6.
• #2135999: Fix for strict options checking in Drush 6.
• Update site_data example extension with new load method.
• Fix naming of hook in api docs.
• be more tolerant about the way the alias gets passed from the frontend
• #2117227 by Ogredude - Missing newline causes syntax errors in vhost.d nginx config when redirects are enabled.
• Copy all makefiles into Debian package.
• Conditinally add subdirs/ to the debian package.
• Fix .deb dependency.
• #2113463: Fix take hosting_platform_pathauto out of experimental.
• #1376466 by Dane Powell: Fixed path not generated when copy/paste is used.
• #1898252 by Dane Powell: Fixed Edit option displayed on existing platforms.

3.4. Other issues

• #1923552: Rename 'Queue runner settings' tab to 'Queue daemon'
• #1834036: Add 'hosting platform pathauto' to the .gitignore
• #1785624: Some Drupal API changes in D7 (and D8) are not used/respected properly
• #1979496: Update upgrade.sh.txt for Drush 5
• #1974752: Document old_uri option for provision-deploy

2.2 was an abortive release, due to missing updates to contrib modules. Use 2.3 instead.

See: http://community.aegirproject.org/2.3

The Aegir team is proud to announce the third release in the stable 2.x release branch!

This maintenance release ships with a huge number of bug fixes since our last stable release, almost a whole year ago. There are also some security improvements for nginx users. See below for the full list of bug fixes. Everyone is encouraged to upgrade.

Also, worth noting is the simultaneous release of our first beta for Aegir 3. Debian packages are now being provided for Aegir 3, so trying it out is easier than ever!

N.B. The 2.2 release was invalid, as the contrib modules included in the drupal-org.make had not been updated.

1. Security improvements for nginx

Previously, Aegir stored SSL cipher and protocol settings per site in Nginx virtualhost configuration files. This included the enabling of SSLv3, which is vulnerable to POODLE attacks [1].

Because these settings were stored via templates, permanently removing SSLv3 support on Aegir-based Nginx SSL environments was not possible. These settings have now been removed from the templates that generate Nginx virtualhost files under Aegir. If you wish to either re-enable SSLv3, or otherwise alter SSL cipher and protocol settings in Nginx, we recommend you do so in the http {} context (e.g, in /etc/nginx/nginx.conf), which are applied globally and are never manipulated by Aegir.

Sites that were running on Nginx and had SSL enabled, should be re-verified to remove those settings.

Apache users (including those using SSL) were not affected.

[1] http://en.wikipedia.org/wiki/POODLE

2. 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 at:

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.

N.B. Issue #2146977: Broken backward compatibility with IP based vhosts may affect those upgrading from 1.x. It appears that running 'verify' tasks on all sites should resolve the issue.

3. 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 :)

4. Known issues

Being really open about our project, we have never hidden the fact that some things, sometimes, do not work in Aegir. Our issue trackers are public, and we've made it a point of honor not only to document clearly what is wrong in our releases as soon as we find out about it, but also to reroll new releases when we fix it.

That being said, 2.2 still has a number of issues and design flaws. This is the list of all issues marked "major" in the queue right now. Most issues are now likely to be fixed in the 3.x development branch, and unlikely to be backported unless considered critical.

As mentioned in the previous section, Issue #2146977: Broken backward compatibility with IP based vhosts is still listed as a 'critical' issue against the 2.x branch. However, it should only affect those upgrading from 1.x, and has a fairly simple work-around. If you come across this behaviour during your upgrade, please post a comment to the issue, so we can confirm that it still exists.

5. Features

#2267057: Pre-upgrade add ctools to 6.x-2.x

6. Bug fixes

Changes to hosting since 6.x-2.1:

• Make it clear that subdomain (foo) and subdirectory name (foo) must be identical.
• #2333911 - Restore the pre-views order of tasks in the queue blocks/lists.
• #2313327 by helmo | tvl: Fixed Unknown options for provision-verify.
• #2163525 by helmo | daften: Fixed Aegir doesn't delete old alias on migration of site.

Changes to provision since 6.x-2.1:

• #2457359: Stop overriding Nginx SSL settings
• Nginx: Stop the POST flood to /autodiscover/autodiscover.xml generated by MS Office/Outlook
• Nginx: Use dummy db fastcgi_param placeholders if any of them is empty
• #2350695 by omega8cc, helmo: Profile is registered twice, also as a module, which causes warning
• Nginx: Remove webform keyword from regex locations - fixes #599
• Nginx: Sync configuration improvements.
• Fix for custom cpuinfo logic.
• #2421543 by notzach: Changing how Apache ServerAliases are defined
• Nginx: Use safe fallback for mysteriously empty $db_port
• Nginx: Use reliable source for db_port to write in the vhost
• #2276557 by zxaos, bgm: allow aegir2-provision package to accept mariadb or mysql
• Nginx: Fix for D8-specific /cron/ location caching (extended mode only).
• Nginx: Fix for D8-specific /cron/ location regex.
• Nginx: Drupal 8 with clean urls enabled should use /cron/ URI.
• Nginx: Sync config templates.
• Detect if the platform stays the same only when site name changes.
• Standardize inline comments.
• #2372653 by helmo: Add --no-autocommit when dumping MySQL tables
• Use $new_name instead of $new_uri to avoid confusion.
• Compare $new_uri with d()->name and not d()->uri in the Site Rename Check.
• Nginx: Helper locations to avoid 404 on legacy images paths (subdir only)
• Nginx: Fix spacing
• Nginx: Add missing variables in subdirectory config template.
• don't allow d() to run before drush is fully initialized
• Nginx: Add the fix for known problem with files/imagecache in legacy D6 sites (again).
• Nginx: Fail early if any required db credentials are empty, to never create broken vhost.
• Nginx: Block semalt botnet (extended boa mode only)
• #2358977 by mrP - [nginx] Aegir redirection to non-install url leads to sites/$server_name/files 404 errors (sub-dir config sync)
• #2373923 by griz - https redirect problem with Nginx (fix tested)
• Nginx: Avoid redirect loops (really fixed).
• Nginx: Avoid redirect loops (fixed).
• Nginx: Avoid redirect loops.
• #2358977 by mrP - [nginx] Aegir redirection to non-install url leads to sites/$server_name/files 404 errors.
• Nginx: Simplify imagecache/styles support.
• Nginx: Remember real site name in $main_site_name and MAIN_SITE_NAME.
• Sync new lines.
• Nginx: proper sync with Apache redirects.
• Revert "Issue #2373923 by griz - https redirect problem with Nginx"
• #2373923 by griz - https redirect problem with Nginx
• Merge remote-tracking branch 'origin/6.x-2.x-backports' into 6.x-2.x
• #2163979 - Check if field_info_field_map() is available to not break support for old D7 versions.
• Make sure that db_port is never empty and defaults to 3306.
• #2266997 by helmo, cweagans: Added Do not automatically enable update module when installing a site.
• Nginx: Update vhosts templates to match BOA improvements #unforkboa
• Nginx: Sanitize aliases in vhost_disabled.tpl.php to avoid: 'nginx: [warn] server name "foo.com/bar" has suspicious symbols'
• Fix spacing in config lines.
• Nginx: Update config includes to match optional BOA features improvements #unforkboa
• Manage extra GRANTS to allow SQL remote access via SSH tunneling which depends on '127.0.0.1' and will not work with GRANTS for 'localhost'.
• Add support for file generated from /proc/cpuinfo on system with no access to /proc #unforkboa
• Ignore paths from OS X
• Backport provision_hosting_feature_enabled (2)
• Backport provision_hosting_feature_enabled()
• Fix typo.
• Shorten and simplify the subdirs checks code.
• Remove legacy subdir code and update checks.
• Remove whitespace.
• Use is_readable() instead of file_exists() when checking alias existence.
• Use is_dir() instead of file_exists() when checking directory existence.
• Use is_readable() check instead of insufficient file_exists() for config includes.
• Remove redundant file_exists() if is_readable() is also used.
• Add little debugging markers.
• Use strict checks: is_file() and/or is_link() instead of file_exists() before attempting unlink()
• Fix for mysterious warning "Could not create directory ." on Hostmaster site Verify.
• Nginx: Fix typo in vhosts templates.
• #2330781 - Use Drush native dt() wrapper instead of not always available t()
• #2329131 by dagomar: Fixed Uninstalled block module causes errors.
• Allow usage with Drush7, now that *.drush.load.inc's aren't being included.
• #2177315 by pwatzeels: Fixed Group permissions on private/temp folder not correct on remote server.
• #2296089 by ergonlogic, cosmicdreams: Fixed Installer can detect incorrect default web group.
• #2169287 by cableman0408: Fixed Setting user name twice (fails non-default installation profile).
• #2275467 by kristofferwiklund: Fixed incorrect variable in Debian postinstall script for Apache 2.4
• Stop false-positive warnings when SSL uses a wildcard.
• #2259461 by Liam McDermott - Remove too aggressive limit_conn directive in the Nginx config templates.
• Revert "change version information for release 2.1"
• #1168758 by helmo | acrollet: Optionally add --include-vcs argument when using drush rsync to sync remote platform.
• Extend provision_drupal_fetch_site with a parameter to specify site to fetch.

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

The Aegir team is is pleased to announce the fifth release candidate for the upcoming Aegir 2.0 release!

This release ships a ton of bugfixes we have found in RC4. We also finalised subdirectory support which, while it still has some issues, is now actually working correctly, even on multiple servers. The IP allocation code for SSL on multiple servers was also fixed, making this probably the most solid multi-server Aegir release ever. We also did some API cleanups that seemed necessary before the final 2.0 release.

Finally, we should also mentionned that the install process was significantly sped up thanks to the use of Drupal.org distributions to ship a single tarball for the hostmaster platform instead of using a makefile to build it from its parts all the times. During out tests, the platform make step went from 60 seconds to 1.5 seconds, an amazing improvement!

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, with 2.x-specific instructions outlined in bold.

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. You should be able to upgrade to 2.x releases from any release in the 1.x series, but it's better to upgrade to the latest 1.x release first.

Known issues

Those are the critical bugs that were found in this release that you may encounter and should watch out for.

• There was a problem in the Debian package, the original uploads were missing some critical files (subdir support and some makefiles). This was fixed in an intermediate package named 2.0~rc5.1.
• If /var/aegir is a symlink, it will be destroyed, see issue #2118857 for a workaround.
• hosting-queued doesn't get properly re-enabled on upgrades, see #2114675 for a workaround.
• Some upgrades fail with mysterious redirection failures, see #2118061 for details.
• Some upgrades may loop over one of the update_N() functions, see #2118917 for details and workaround.
• Upgrading through Debian packages removes the aegir.conf Apache configuration file, dropping all sites, during the upgrade, see #2121263.
• Ubuntu sausy has some changes in apache config wich breaks Aegir #2155705

Detailed list of changes

API CHANGES

• remove version pinning in hostmaster, our release process now again needs to modify only one makefile (#2002114)
• #1986928: Provide 2.x upgrade guidance for services
• #2099889: More hosting_features checks in _drush_load hooks?
• #1882708: Unused 'release_id' field in 'hosting_platform'
• #2012508: hosting_context_name returns '@' if node not found
• #1283738: Add new hook provision_drupal_create_directories in _provision_drupal_create_directories
• the package name changed (for example) from aegir-hostmaster2 to aegir2-hostmaster, compatibility shims are available for people having installed aegir2 before, but they will be dropped in 2.0, so make sure you upgrade to this release before upgrading to aegir 2.0

NEW FEATURES

• aegir install time reduced by about 60 seconds (on a cable uplink) by using Drupal.org distributions (#2002114)
• #2001964: Upgrade Views Bulk Operations 6.x-1.16
• #2099057: Allow _provision_drupal_create_directories to skip chmod
• #2100251: Implement post-enable hook for 'hosting_*' modules
• #2020075: Refactor subdirs to use proper Config class(es)
• #2020079: Multi-server subdirectory support
• #2096629: hook_provision_drupal_create_directories_alter by ref
• #2086009: Logo Cannot be changed / disabled
• #2069387: Support nonstandard ports on hostmaster-install command
• #2074681: Ports are hardcoded in hostmaster.profile
• #2103173: Provide an example of saving data to a site context

BUG FIXES

• #2110057: Key used for signing debian package has expired
• #1635628: do not talk about a makefile if installing over an existing platform
• #2103173: Provide an example of saving data to a site context
• #2109637: upgrade.sh script fails to checkout 6.x-2.x
• #2085077: Invalid argument supplied for foreach() hosting.ip.inc:39
• #2102341: Differentiate between a feature being disabled vs absent
• #2029799: Error deleting a platform: Call to a member function succeed() on a non-object
• #1971348: Site aliases get chopped if longer than 50 characters
• #2071317: Incorrect SSL IP is deployed to servers in a web pack
• #2098289: Backup task does not detect failed database dump
• #2098389: subdirs kicks in even when subdirs module is disabled.
• #1189576: can't disable the DNS service from the frontend
• #1931000: Missing drush backend output in frontend log
• #2077793: Queue daemon collecting quotes
• #2097689: clean_urls don't work well with subdirectory
• #2097363: Add site spins forever
• #1387578: hosting_queues_cron_cmd makes unwarranted assumptions about bash availablility
• #2084963: SSL vhost does not respect Alias redirects
• #2061509: List of platforms is no longer updated to match install profile clicked at node/add/site
• #2046783: Task dialogs won't open after clearing the cache

An error in the manual portion of our release process resulted in the incorrect version of the code-base being built. See the release notes for 2.0-rc3 for relevant changes since 2.0-rc2.

Known bugs

In addition to those listed in the release notes for 2.0-rc3, note that some people have experienced problems with downloading a patch in the main Aegir makefile. This is most likely due to problems with drupal.org's SSL certificate. If you are experiencing such an issue, there is a simple work-around: edit the aegir.make file in the provision/ directory to make the path use http:// instead of https://.

For a Debian-based system (including Ubuntu), this would look something like:

$ sudo vi /usr/bin/drush/commands/provision/aegir.make

For 'manual' installs on other OS's, it would probably be:

$ sudo vi /var/aegir/provision/aegir.make

Change the line:

projects[drupal][patch][] = "https://drupal.org/files/common.inc_6.28.patch"

to read:

projects[drupal][patch][] = "http://drupal.org/files/common.inc_6.28.patch"

Then re-run the install. On Debian/Ubuntu machines:

$ sudo apt-get install aegir2

On manually installed systems (CentOS, etc.) as the aegir user:

$ drush hostmaster-install

Detailed list of changes

API CHANGES

None.

NEW FEATURES

None.

BUG FIXES

• Fixed makefiles to point to proper versions of projects.

The Aegir team is pleased to announce the third release candidate for the upcoming Aegir 2.0 release.

This release mainly fixes a couple critical bugs in 2.0-rc2 that were causing problems when sites were being cloned or renamed. We've added a couple small features, such as additional options during hostmaster-install, and allowing the redirect to the Welcome page to be turned off. Also, we've made a small addition to the API, in that there is now a hook available (hook_provision_drupal_create_directories_alter()) to allow altering the directories created when a site installed.

In order to better support PHP 5.4, we have added a patch to Drupal core to suppress E_STRICT warnings. These were harmless, but annoying. They were caused by a changed in PHP error-reporting in PHP 5.4, and the Views module's maintainers' desire to remain backward compatible with PHP 4. For more details, see: #2060727: Patch Drupal core to suppress E_STRICT warnings on PHP5.4.

A number of pending issues require a new stable release of Drush (5.10), so we will work with the maintainers to help get a new release out.

Known issues

Our release process is still done by hand instead of being more automated because we can't use our aegir distribution as core (issue #1991764).

Issue #1931000: Missing drush backend output in frontend log has been fixed, but may require a patch to Drush for the use of hosting-queued.

Subdirectory support is still very preliminary and needs a number of issues to be fixed before completion, see #2046167 for details. Note that this will not block a stable release, since this feature is 'experimental', and additional re-factoring can occur during the stable release cycle.

Detailed list of changes

API CHANGES

• #1283738 by halcyonCorsair, cweagans: Allow other commands to add or alter the directories to be created.

NEW FEATURES

• #2069387 by cweagans, mstenta: Support nonstandard ports on hostmaster-install command.
• #2067617: Allow hostmaster-install to accept '--working-copy' option.
• Allow the redirect to the welcome page to be turned off.

BUG FIXES

• Add E_STRICT patch to test openatrium makefile so tests will pass on PHP 5.4.
• #2067603: Fix original and cloned site pointing to the same database.
• #2048653: Ensure mysql is secure before proceeding with hostmaster install.
• #2060727: Patch Drupal core to suppress E_STRICT warnings on PHP5.4.
• #2038279: Warn of invalid account email on site install.
• #2055949: Fix migrate drops wrong database when domain name changes.
• #2074681 by cweagans, mstenta: Fixed ports are hardcoded in hostmaster.profile.
• Use custom functions for block visibility.
• #1940378: Fix PHP 5.4 warning by initializing an object variable prior to assigning properties.
• #2050881: Call drush.php via php, since it isn't executable when installed via PEAR.
• Enable platform site-list block, since it had to be renamed.

The Aegir team is pleased to announce the second release candidate for the upcoming Aegir 2.0 release.

This release mainly fixes our project makefile that, due to an error in our build process, did not pull in the latest code. As a result, installing 2.0-rc1 actually installed a 2.0-beta2 codebase. While changes between 2.0-rc1 and 2.0-rc2 have otherwise been minimal, we invite you to explore all the new features and bugfixes in 2.0-rc1.

Note that we have taken this opportunity to update our external dependencies, as well.

Known issues

Our release process is still done by hand instead of automated because we can't use our aegir distribution as core (issue #1991764).

Issue #1931000: Missing drush backend output in frontend log has been fixed, but may require a patch to Drush for the use of hosting-queued.

Subdirectory support is still very preliminary and needs those issues to be fixed before completion, see #2046167 for details.

Issue #2046783: Task dialogs won't open after clearing the cache was the result of updating our dependencies. Refreshing the page is usually sufficient to make modal dialogs work again. It looks like this was probably specific to the development environment, as we can no longer reproduce it.

A critical bug was discovered: Issue #2055949: Migrate drops wrong database when domain name changes. It has been fixed in 6.x-2.x, and a patch for 2.0-rc2 is available.

Detailed list of changes

API CHANGES

• Update external dependencies.

NEW FEATURES

none

BUG FIXES

• Add dependency on jquery_update, so we can use the more recent version of modal_dialog.
• Enable login and nav blocks explicitly.
• treat symlinks as existing, fixes #2046249

The Aegir team is pleased to announce the first release candidate for the upcoming Aegir 2.0 release.

This release mainly targets a few critical bugs that were found in the second beta, mostly related to ongoing Views, Drush integration and access control. We also introduce a number of new features and finally drop support for provisioning Drupal 5 sites completely (for real this time!). Along the way, we did quite a bit of API cleanup.

While we are in feature freeze, we have continued to add some UI improvements, since they don't affect the API. We've added some long-standing UI enhancements, and fixed a number of bugs in the views integration and other usability problems, as well as overhauling our access control. Significant improvements to the package-management system have also been introduced.

Our only remaining critical bugs are basically waiting on a new release of Drush, upgrade testing on Nginx and some contrib upgrade guidance documentation. If no other critical bugs are discovered during the time it takes us to fix these, we should move on to a full release of Aegir 2.0!

Known issues

Our release process is still done by hand instead of automated because we can't use our aegir distribution as core (issue #1991764).

Issue #1931000: Missing drush backend output in frontend log has been fixed, but may require a patch to Drush for the use of hosting-queued.

Subdirectory support is still very preliminary and needs those issues to be fixed before completion, see #2046167 for details.

Detailed list of changes

API CHANGES

• #1034520: Cleanup package instances when deleting sites and platforms.
• #1830220: Drop support for Drupal 5.
• #1975086: Move log parsing and status updates to seperate functions and call them from a shutdown function.
• Pass the entity type when we're sync'ing package instances.
• Save the platform field when creating a package instance record.
• Move to individual operation callbacks for VBO tasks.
• #2022849: Record disable and delete backups in the database.
• #2031491: Rename SSL permission to be more descriptive.
• Clean up hosting_node_grants().
• Add 'administer' permissions for platforms and servers, and allow platforms to be viewed.

NEW FEATURES

• #905326 by ergonlogic, crea: Improve file path changes.
• #1201174: Make UID1 username configurable.
• #1345118: Make platform access control an autocomplete form.
• #1515416 by ergonlogic, helmo, Deciphered: Replace listing of sites and platforms using a package with a view.
• #1975086: Add 'update status' button to tasks.
• #2005310: Add VBO operations to platforms view.
• #2006074 by Deciphered: Enable backups via VBO.
• #2025787 by omega8cc, ergonlogic, anarcat: Open site goto link in a new window/tab.
• #2022813 by Deciphered: Expose backups to Views.
• #2027269: Update a task's status after all Drush operations are complete.
• #2031491: Review and update permissions for all roles.
• #2031765: Clean up VBO operations with Action Permissions.
• #2035873: Show package 'popularity' on platform package view
• #2036283: Make Aegir aware of site-specific packages.
• #2036793 Ignore hidden modules and profiles.
• #2037045 by helmo, ergonlogic: Change some log statuses to better match Drush's log styling.
• #2037965: Clean up hosting-pause.
• #2038279 by ergonlogic, Jon Pugh: Validate email during site install.
• Display all validation errors when adding a client, and limit to 20 suggestions.
• Flag rollbacks as warnings in our task logs.
• Handle package page views separately for sites and platforms.
• Update default hosting_site views to use new access plugin for blocks, and add a couple more displays for non admin listings.
• Add Views access plugin for hosting_site and hosting_package.
• Add views handler to filter packages by status.

BUG FIXES

• #1238618: Fix client form validation.
• #1263264 by ergonlogic, recidive, anarcat: Specify a type when getting a package, to avoid collisions.
• #1647830 by sambonner: Fix Incorrect ownership of directories under sites/example.com/private/files/.
• #1861898 by ergonlogic, Jon Pugh: Don't hardcode the types of entities to which we can attach tasks.
• #1975086 by helmo | anarcat: Fixed updating a task when there is none.
• #2025355: view platform' permission broken
• #2026417: Disambiguate site operations.
• #2031491: Fix roles.
• #2031747: Fix Views block placement and visibility.
• #2038891: Add 'client_email' option to 'provision-install-backend'.
• #2038891: Switch from '--invoke' to '--strict=0' for backend calls.
• #2040285 debian: properly detect webserver, again
• #2044251 drush command '@none provision-save' could not be found
• #2045907: Remove extra tabs from deleted platforms.
• Fix php 5.4 issue
• Add missing unicode include for UID1 name validation.
• Fix update hook name.
• Only register shutdown function to update task status in the context of a front-end task.
• Don't display package block on profiles.
• Only show link to add clients on site form to those with proper permissions.
• Override hook_access functions for node_grants when hosting_client is enabled.
• Register node type in hosting_task's Hosting feature.
• Clean up Views exposed forms.
• Fix Views block placement and visibility.
• Only display client sites block on the 'view' tab.

The Aegir team is pleased to announce the second stabilization (beta) release of the Aegir 2.x branch.

This release mainly targets a few critical bugs that were found in the first beta, namely IP allocation on non-SSL and non-cluster sites which was completely broken and bugs the Debian package. We also introduce a few new features and finally drop support for provisionning Drupal 5 sites completely.

While we are in feature freeze, we have continued to add some UI improvements, since they don't affect the API. We've added some long-standing UI enhancements, and fixed a number of bugs in the views integration and other usability problems.

We are down to only one active critical bug. If no other critical bugs are discovered during the time it takes us to fix it, we should move on to our first release candidate!

Known issues

Our release process is still done by hand instead of automated because we can't use our aegir distribution as core (issue #1991764)

Issue #1931000: Missing drush backend output in frontend log has been fixed, but may require a patch to Drush for the use of hosting-queued.

Subdirectory support is still very preliminary and needs those issues to be fixed before completion:

• Nginx support missing (issue #2020091)
• If example.com/foo is created, the example.com virtual will be overwritten and the site inaccessible under that domain (issue #2020089)
• Multi-server support is untested (issue #2020079)
• Code needs to be refactored to the new 2.x API (issue #2020075)

The move to Views has highlighted some additional issues:

• #2025355: view platform' permission broken
• #2005310: No actions available on platforms view

Fixing #2027269: warnings and errors in front-end pre- and post- hooks are ignored for task status required a new Drush commandfile, and thus a 'drush cc drush' if upgrade between an alpha/beta release and HEAD.

The debian package still doesn't properly configure the webserver, a patch has been committed and a workaround is available in issue #2040285.

New features

• #600350: provide a nice "history" of ran tasks
• #1988642: Add site by platform
• #1912238: automatically build and upload aegir 2.x packages
• #585830: usability story: "How do I create a client?"
• #1830220: Drop support for Drupal 5 in 2.x
• #1212086: Platforms should be locked by default
• #1403208: Add additional roles
• #1174440: provide a way to show site's DB username/password in the frontend
• #606120: Disabled sites should be class hosting-warning, enabled but problematic sites should be hosting-error

Bug fixes

• #1992254: restarting the mysql server crashes hosting-queued
• #1761932: Explain that updates will require the verify task to run
• #1603702: allows creation of SSL site even if there are no IPs available
• #1130992: User 1 has lost the ability to create platforms
• #1126638: two sites can take the same server IP for SSL
• #1994000: Nginx looking in wrong place for SSL setup information
• #2023621: Unable to allocate IP address for certificate, disabling SSL.
• #1929454: hosting_cron.modules requires hosting_site.module but lacks a dependency.
• #2014589: Views-based package list omits module/theme version
• #2005246: It is possible to disable Hostmaster site via bulk site operations
• #2025533: Mod Rewrite and Apache.conf symlink not created with debian package - beta2

The Aegir team is pleased to announce the first stabilization (beta) release of the Aegir 2.x branch, after nearly 3 weeks of development since our second alpha release. While we had expected an additional alpha release prior to the beta cycle, development on outstanding features went smoother than foreseen. We've added some significant features, and fixed a couple bugs and (again) made some important improvements to our API.

This release marks our feature freeze. The intention is to limit any further changes to only critical and major bug fixes. However, exceptions may be granted on a case by case basis. Our development efforts will now move to tackling all release critical bugs. Once all of these are fixed, we'll move on to our release candidate (RC) phase. That said, we expect this release to be sufficiently stable that we intend to run it in production at Koumbit soon.

Release overview

This release introduces a major new feature into Aegir core: support for installing sites in subdirectories (example.com/foo, example.com/bar, etc.). This has been our number one feature request from higher education institutions, and so we hope that this will enable greater adoption within that sector. While categorized as an "experimental" feature, we feel our approach is sufficiently strong that we're considering merging this into our core site functionality.

Additional new features include a nice homepage, fixes to SSL support and IP allocation on clusters, and we've added a couple new roles.

We've also tackled a number of bugs, especially in the Debian package, which now supports installing Aegir on Nginx servers. We've also fixed some issues introduced with the new views code, and improved nginx support.

The project's Debian repo now includes Drush 5.9, and we have migrated the 'aegir2' packages to the Testing repository.

Known issues

• the debian package shows a lot of garbage when installing from scratch, which is almost harmless except that we don't see the login URL, use drush @hostmaster uli to get a new one, fixed in issue #2002076
• SSL support was severely broken for single servers and could lead to loss of the SSL certificate copies when a non-SSL site is installed. See commits f0980e0..9b86038 in Provision for fixes. (fixed in issue #2023621)
• the Debian package is severely broken - in most configuration (e.g. clean installs but not upgrade) the install will just fail with a permission denied. See commits d4efa37 and 56d1718 for fixes.

These are related to drush:

• some warnings and errors may not show up in Aegir's task logs, making it believe tasks succeeded when the actually failed. this affects only hosting-queued. (issue #1931000 / issue #1982502)
• our release process is now done by hand instead of automated because we can't use our aegir distribution as core (issue #1991764)

Subdirectory support is still very preliminary and needs those issues to be fixed before completion:

• Nginx support missing (issue #2020091)
• If example.com/foo is created, the example.com virtual will be overwritten and the site inaccessible under that domain (issue #2020089)
• Multi-server support is untested (issue #2020079)
• Code needs to be refactored to the new 2.x API (issue #2020075)

API changes

• Multiple files can be managed in a single context now (see issue #2000038, issue #1784108)

New features

• Support for installing in subdirectories (issue #705026)
• Proper homepage on startup so non-logged-in users don't see an error page, and new users have basic instructions (issue #1793740)
• SSL support for clusters should now work properly (issue #2000964)
• New roles added: 'aegir platform manager', 'aegir administrator' (issue #1403208)
• Convert list of platforms to use views (Issue #1876350)

Bugfixes

• Debian package support for nginx was severely broken issue #2001142
• the views bulk operations version shipped with alpha2 had security issues, see issue #2001964
• an update hook was incorrectly named, and has since been fixed. The updates should not be destructive, but may output errors.
• Placement of a number of our new Views-based blocks was omitted from the install profile, and so won't appear on a fresh install. These can be manually placed on the blocks page.
• fix warning "Invalid argument supplied for foreach()" (issue #2005698)
• fix "Unknown options for provision-save" error (issue #1972286)
• removed hardcoded checks for IP addresses in settings.php that belong to core (issue #2013683)
• Views filter for status does not tell what to filter for (issue #1997088)
• nginx cloaks database credentials properly now
• configure nginx to properly talk to the default php-fpm configuration in Debian (issue #1635622)
• lots of fixes for the Debian package, including
  • Silence garbage in the install output (issue #2002076)
  • nginx support in sudoers file (issue #2001142)
  • nginx autodetection in Debian package (issue #2003712)

The Aegir team is pleased to announce the second preview (alpha) release of the Aegir 2.x branch, after nearly 3 months of development since our first alpha release. We've squashed a number of tenacious bugs, added some nifty features, and made some important improvements to our API. We expect at least one more alpha release before we call a feature-freeze, and begin out stabilizing and cleanup (beta) release cycle.

During this release cycle, we also began work on Aegir 3, a more-or-less straight port of Aegir 2 to Drupal 7. We continue to sync changes in 2.x to our 3.x branch, and look forward to continuing the port (and beginning to add new features) as soon as we've released our first stable 2.x release.

Our next alpha release will target getting sub-site support (example.com/site1, example.com/site2, etc.) into Aegir core as an experimental feature. This has been our number one feature request from higher education institutions, and so we intend to incorporate it into Aegir 2, in order to enable greater adoption within that sector. We have a fairly detailed implementation plan, and so feel confident that we can incorporate this major feature, in fairly short order.

Release overview

This release features improvements to the IP management mechanisms that were broken in the last alpha1 release. We now manage IP addresses individually, and check if an IP is in use before allowing it to be deleted.

We also finally leave the files alone on spokes in the multi-server model, a long-standing bug in the 1.x series that led to data loss. A lot of work was done to standardize the Nginx configuration to allow for simpler, yet optional, configurations that leave the admin in charge of choosing the optimisation methods.

Also, we've moved Hosting and Eldir back to their own projects, and are now included via our makefiles. This simplifies building custom install profiles, though it complicates our release process somewhat. We've also added a drupal-org.make that will eventually allow proper distribution bundling of Aegir.

Finally, we've moved to using Views and View Bulk Operations for our lists of sites, platforms and packages. While there remain some rough edges, this will allow much easier customization of our principal UIs. It has also significantly reduced the custom code we have to maintain, in favour of exported Views, which simplifies maintenance.

Known issues

• the Debian package support for nginx is severely broken #2001142
• the views bulk operations version shipped with alpha2 has security issues, see #2001964
• the debian package shows a lot of garbage when installing from scratch, which is almost harmless except that we don't see the login URL, use drush @hostmaster uli to get a new one, fixed in #2002076
• an update hook was incorrectly named, and has since been fixed. This may cause the hook to be run again, if the site is upgraded to a newer version. The updates should not be destructive, but may output errors.
• Placement of a number of our new Views-based blocks was omitted from the install profile, and so won't appear on a fresh install. These can be manually placed on the blocks page.

API changes

• deprecate hosting_ip_delete_revision(), dupe of hosting_ip_delete() now that revisions are gone (8 weeks ago)
• allow running tasks that appear to be running with --force
• remove deprecated DEBUG flag in debian package
• #1785624: Some Drupal API changes in D7 (and D8) are not used/respected properly
• #1945950: Rename provision_drupal_sync_site_back()
• #1083366: Make the spokes authoritative for files/ and private/ directories
• #1812338: Refactor sync back
• a new control file has been introduced in /etc/nginx/basic_nginx.conf to force the nginx configuration to be the "simpler" one (see #1635596: nginx: do not decide the policy for users)
• #1987026: Move generated platform drushrc.php to sites/all/drush

New features

• #1929372: Flag tasks with logged warnings
• #1515416: On a package page, show table listing sites and platforms using the package
• #1853620: Add db_name to site summary
• #1681904: Ability to configure a url to redirect to in site configuration.
• #1968226: manage each IP individually on the server level - manage IPs individually
• add uninstall command
• Nginx Security: BEAST attack protection and fix for PCI compliance.
• #1980136: Allow setting default profile from the front-end.
• #588728: Replace custom lists with Views and VBO for sites, platforms and packages.

Bugfixes

• #1930670: Duplicate entry 0 for key PRIMARY in hosting_ip_addresses when installing / upgrading
• #1907028: user warning: Table 'XXX.hosting_ip_addresses' doesn't exist
• #1961920: nginx: [emerg] invalid number of arguments in "limit_conn_zone" directive in /etc/nginx/conf.d/aegir.conf
• #1923490: Incorrect error message in aegir-provision2.preinst
• #1901508: "gzip --rsyncable" is invalid on OS X
• #1678528: Database deleted on edge cases
• #1930740: provision-delete leaves a drushrc.php lying around
• Nginx: Do not override Nginx name with fake Apache name.
• #1990370: Enable Hosting feature dependencies.

Other

• #1923552: Rename 'Queue runner settings' tab to 'Queue daemon'
• #1834036: Add 'hosting platform pathauto' to the .gitignore
• #1785624: Some Drupal API changes in D7 (and D8) are not used/respected properly
• #1979496: Update upgrade.sh.txt for Drush 5
• #1974752: Document old_uri option for provision-deploy

The Aegir team is pleased to announce the first preview release (alpha) of the Aegir 2.x branch, after almost 2 years of development. We have been pretty busy with the maintenance of the 1.x branch, so development has been sometimes intermittent, but it is not over yet!

This release is only a first of a series of alpha releases that are tailored to make upcoming changes available to a wider audience than people ready to install from git, but also to make features more widely available and tested. More alpha releases will be published on a more regular basis in the weeks to come as more features from the new provisional roadmap are implemented. We are still considering the following:

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) - done! Now onto testing and fixing the actual bugs linked from #941870

We would like to get those in 2.x, but since no one has really started significant work on those, we are more likely to simply postpone those to 3.x at this point.

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

Also, since every single attempt at providing a proper timeline for the final 2.0 release has failed miserably, we'll just stop trying our luck and just give up on a formal timeline. Instead, we'll just do the freaking work. :) Also remember that the port to Drupal 7 has been postponed to Aegir 3. Aegir 1 and 2 both support provisionning Drupal 7 sites, but the frontend is running Drupal 6. We are aiming for a "straight port" (no rewrite) of the frontend for Aegir 3.

1. Major changes

This first alpha already packs a lot of changes. Those release notes detail the changes since the 2.x branch was first created, all the way back two years ago, when 1.0 was released. Of course, we are not detailing all the changes made in the 1.x series that are all part of the 2.x, but only the changes specific to the 2.x release.

• SSL improvements:
  • IP allocation was moved to the backend to the frontend
  • SSL certificate generation now has saner defaults (e.g. 2048bits)
  • better error handling

• Drush 5 support

  • includes better support for archive-dump command
  • means we also drop the dependency on drush make 2.3, now included in Drush 5
  • support for Drush 4 has been dropped, the minimum version is now 5.5

• Debian package improvements and changes

  • Nginx support in the Debian package
  • now a "native" debian package
  • package name changed: it is now aegir2, aegir-provision2, etc, to avoid overwriting the previous package - note that aegir 1 and 2 can not be installed in parallel
• Nginx improvements:
  • fixed support for nginx 1.3 and newer
  • better defaults for caching
  • SSL and Nginx are now officially supported (not marked as "experimental")
• New modules:
  • the hosting-queue-runner module is now merged into core as hosting-queued
  • "pack" module, designed as a lightweight replacement to the "cluster" module, now available as an experimental extension
• Hosting-queued improvements
  • run with a lower priority ("niced")
  • improved portability and reliability of startup script
  • enabled by default in the Debian package
• Code refactoring and improvements:
  • now using the Symphony autoloading code
  • fix coding style in a lot of source files
  • improved builtin test suite
  • eldir is split in its own module again, allowing for porting it more easily to Drupal 7

A more detailed log of bugfixes and improvements is available below.

2. Major API changes

Those changes are, as usual, more explicitly documented in the upgrade path documentation.

• hosting-task now needs a --force argument to run a non-queued task
• functions that were deprecated in 1.x are now removed
• the email and client_email database fields are now removed from client and site node types
• numerous changes to the IP allocation and SSL management code

Please note that the 2.x API is still not considered stable and may change without warning until 2.x is fully stabilized, see our release process for more information.

3. 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.

Note that you should upgrade to the latest 1.x release (currently: 1.9) before attempting the upgrade to 2.x. This is especially important if you are running a pre-1.0 release (poor you!).

It is still imperative that you read the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade.

4. 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 :)

5. Features and improvements

In addition to the "major changes" mentioned above, the following should also be noted.

• #1830994: Login directly via 'login' link
• #1853588: Sort Install profiles on Site add form
• #709862: Allow drush modules to add to apache vhost config template
• #1861896: Make $type argument of function hosting_available_tasks() optional.
• #1843198: Add Content top and bottom to Eldir.
• #1826074: Add tests to ensure site directories are migrated
• #1464220: Support alternative 'Hostmaster' profiles
• #610040: Add X links on listing pages
• #710834: notify clients on site migrations
• #1260066: Allow use of the working copy option when creating a platform
• #1047992: exportable backups
• #1189556: Pull the queue runner into Aegir 2
• #1408410: Add microcaching to Nginx config by default
• #1138104: Tiny module to automatically fill in platform publish path based on title

6. Bugfixes

This is a non-exhaustive list.

• #1735174: server verification fails after configuration on pack slave servers
• #1798252: reload hosting-queued on upgrade
• #1898260: platform form should allow editiong if platform is not verified
• #1435098: Client name validate sometimes gives erroneous results
• #1591720: Illegal choice when selecting sites to verify
• #1587232: All radios labels in forms use incorrect vertical-align property value (middle)
• #1218130: checking "Hide platforms with non-default profiles" breaks D7's minimal and standard profiles
• #1227954: hosting_quota lacks a feature.module_name.inc
• #528064: h2 bigger than h1 in content
• #460974: improve queue admin form
• #1855486: Patch to Remove some Notices
• #1881868: SA-CONTRIB-2012-080 hasn't been applied to 6.x-2.x
• #1873384: 'Silence warning' commit broke 6.x-2.x
• #1843078: aegir 2.x debian packages fail to install
• #1829430: drush hosting-tasks broken
• #1146014: A user can see sites that don't have a client associated.
• #1256508: path aliases for deleted sites are not deleted
• #1249892: Checkboxes on provision page not aligned
• #941870: failure to copy SSL certificates should abort tasks
• #1334950: permissions on /var/aegir/config/server_NAME/SERVICE prevents access
• #1471928: provision-save: Unknown options: --context_type, --platform, --server, --db_server, --profile, --client_name, --aliases
• #1751006: Make is called incorrectly
• #1750974: Unable to pass working-copy or backend-only to hostmaster install
• #1204990: Drop old database when re-deploying a site.
• #1734500: Can't run tests with Drush 4.6
• #1433406: Make hosting (specifically hosting-dispatch) work with Drush 5
• #1690472: Declaration of Provision_Service_null::__call() should be compatible with that of Provision_Service::__call() null.php:27
• #1266484: Cannot verify Drupal 7.8 with PHP 5.2
• #1612044: upgrade from 1.7 to 2.x fails because of drush 5 command file cache
• #1358768: 6.x-2.x generates multiple Undefined property errors on hostmaster install

7. Known issues

The Debian packages were not uploaded correctly on the release day, and have been unblocked only on 2013-12-12 14:45 (UTC-5).

This section documents all the older releases in the 1.x release cycle.

The Aegir team is proud to announce the tenth release in the stable 1.x release branch! This release ships a moderately critical security fix (see the Security fixes section below) and a number of bugfixes that have accumulated in the issue queue since the 1.9 release. Everyone is encouraged to upgrade.

We also want to announce that ergonlogic and helmo have joined the list of core maintainers supporting the core development of the Aegir project. Along with the existing commitments of the Aegir core maintainer team, Aegir is well assured of continuous development and long term maintenance.

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 releases prior to 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or 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!

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 :)

3. Known issues

Upgrades may fail if the SSL certificates are actually symlinks to files not readable by Aegir, a rare but legitimate use-case. A fix is available in git, see #2046249 for more information.

Aegir 1.x depends on Drush 4.5 or 4.6, which are available only in Debian squeeze backports (old stable!), which may make fresh installs or careless upgrades impossible. To workaround this issue, install the Drush package directly from backports:

wget http://backports.debian.org/debian-backports/pool/main/d/drush/drush_4.5...
dpkg -i drush_4.5-2~bpo60+1_all.deb

See this page for other mirrors.

Because of a little fumble in the 2.0-rc2 release process documentation, a development build of Aegir 1.x has overwritten the 1.10 official release in the stable repository. Since that development build only has the fix for #2046249, we haven't restored the previous build and thefore the version number of the Debian package is 1.10+246.efcd0a3 instead of 1.10. However, this also means that the hostmaster platform directory will be named hostmaster-1.x instead of hostmaster-1.10, which will make upgrades to other development releases require manual creation of the platform.

4. Features

• #1781832 by Steven Jones: Added hosting_available_tasks() should invoke alter.
• #1760962 by Jon Pugh: Added Allow any hosting task to flag itself for needing a provision-save.

5. Security fixes

• Fix access control to sites.

See also the security advisory (SA-CONTRIB-2013-059) for more information.

6. Bug fixes

• #1990370 by ergonlogic: Enable Hosting feature dependencies.
• #1435098 by Steven Jones: Fixed Client name validate sometimes gives erroneous results.
• #1585820 by Steven Jones: Fixed Can't disable the 'client" feature.
• #1573162 by mig5, Steven Jones: Fixed Drush hosting_task_()%task_rollback() invocations are never executed.
• #1513678 by Jon Pugh, fastangel: Fixed Hooks based on TASK_NAME should handle task names with dashes in them.
• #913228 by Steven Jones: Fixed Unresponsive submit button in platform migration form.
• #1441970 by Steven Jones: Fixed Client Block assigned by default to non-existing region.
• #1441970 by jlscott: Fixed Client Block assigned by default to non-existing region.
• #1597648 by jlscott: Fixed Hosting Queues Summary Block is stale.
• #2044251: Remove '@none' from call to drush_invoke_process(), since it isn't supported in Drush 4.5.
• #1678528 by helmo: Fixed Database deleted on edge cases.
• #1912666 by ergonlogic: Fixed Stable manual 6.x-1.x install test failure.
• #1912666 by ergonlogic: Fix command to run tests for 6.x-1.x.
• Nginx: Fix typo in the location regex.
• Nginx Security: BEAST attack protection and fix for PCI compliance.
• #1906900 by fall_0ut - Nginx microcaching not disabled on localized/prefixed admin URIs.
• Nginx: Make upload progress configuration compatible with latest release of Nginx extension and integration module for Drupal 7.
• Nginx: Move some dynamic directives up in the location.
• Nginx: Better protection for private URLs from bots/spiders (2)
• Nginx: Improve locations for static files.
• Nginx: Better protection for private URLs from bots/spiders.
• Nginx: Add support for http://drupal.org/project/js module.
• Nginx: Improve no-cache exceptions for known AJAX and webform requests.
• Nginx: Improve performance for dynamic requests and reduce logging 404 errors.
• Nginx: Remove duplicate location - already protected in the server template.
• Nginx: Do not use device-specific, never working paths for Boost cache.
• Nginx: Make json compatible with boost caching but dynamic for POST requests.
• Nginx: Add Wysiwyg Fields support.
• Nginx: Do not block spiders on URIs with event/calendar regex match.
• Nginx: Avoid breaking WordPress import when WP-specific URI is used.
• Nginx: Avoid caching /civicrm* and protect it from bots.
• remove perlism in sed which would never match (\s).
• explain why we do the crazy sed on dump (mysql bug)
• #1786702 by clemens.tolboom - be nice to non-aegir backups like drush archive.
• #1788398 by marvil07: Fixed Force dependency to drush < 5.
• add missing robots and files/ rules to SSL hosts.
• remove redundant paramenters to the CSR, fix email to use a standard default.
• clarify comment on self-signed certificates.
• #941870 - check for errors when copying certificates.
• improve error handling in SSL key generation.
• bump up the SSL key size to 2048 bit.
• clarify the SSL key signing code.
• don't encrypt SSL keys only to decrypt them after.
• #1741814 by wamilton: Fixed Support For Non-Alphanumeric MySQL Passwords in provision-backup, migrate, and clone.
• #1612252 by mig5, Steven Jones: Fixed 'site_offline()' variable needs to be 'maintenance_mode()' in Drupal 7.
• #1440646 by tstoeckler, cafuego, mig5: Make Drush be runnable as Root with Provision installed.
• #1734500 by Steven Jones: Fixed Can't run tests with Drush 4.6.
• move files and robots.txt rewrite rules to the vhost.
• #1108810 - protect the complete private files directory.

The Aegir team is proud to announce the ninth release in the stable 1.x release branch! This release ships two minor security fixes and various bugfixes that have accumulated in the issue queue since the 1.8 release.

We also want to announce that Omega8.cc is joining the growing list of organisations financially supporting the core development of the Aegir project. In a partnership with Koumbit.org, Omega8.cc is dedicating money to make sure Antoine Beaupré, one of the core team members, can dedicate one day a week of his time on raw Aegir development. Along with the existing commitments of Computerminds (Steven Jones), mig5 (Miguel Jacq) and the existing commitment of Koumbit.org, Aegir is well assured of continuous development and long term maintenance.

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 releases prior to 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!

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 :)

3. Features

No features were added in this release.

4. Security fixes

• Filter Drush log messages properly when viewing task logs.
• Properly exit after calling drupal_access_denied() on package/task nodes.

See also the security advisory (SA-CONTRIB-2012-080) for more information.

5. Bug fixes

• #1550284: Fixed Warningns after enabling 'web pack'.
• #1549210: Fixed Drush 'failed' errors are not correctly logged.
• #1503824: Fixed hosting_site_count() ignores disabled sites.
• Fix for compatibility with Nginx 1.3.0 or newer.
• #1555398: ensure the master server in a Pack is given a MySQL GRANT, if it was not also @server_master
• Add more verbosity to the notorious 'failed to fail' error, pointing to an item in the FAQ.
• #1573004: provision-migrate fails with 'Dummy connection failed to fail: mysql: option -e' requires an argument on Debian Wheezy
• #1573182: Verifying a platform should abort if it can't be bootstrapped<
• #1552228: Nginx configuration for limit_conn should be compatible with version >= 1.1.8
• #1454316: Fixed Provision recurses infinitely on reading in context.
• #1504120: Fixed Script user of remote servers is ignored
• #1205956: Document the Provision API
• Only errors 500 and 503 are supported in fastcgi_cache_use_stale (Nginx).
• #1544144: Use $server_name instead of $host in all sites/ paths to avoid broken URLs to static files for domain aliases in D7 (Nginx).
• Do not cache http auth requests. Use compact microcaching config (Nginx).
• Use separate cache for spiders/bots (Nginx).
• #1528996: Nginx microcaching should use fastcgi_cache_valid with 5s only for 403 error.

6. Known issues

No know issues at this time.

The Aegir team is proud to announce the eighth release in the stable 1.x release branch!

This release ships various bugfixes that have accumulated in the issue queue since the 1.7 release, including a lot of fixes on Nginx 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 releases prior to 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!

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 :)

3. Features

No features were added in this release.

4. Bug fixes

• #1510572: Fixed Why do we use mktime() instead of time()
• #1185690: Fixed hosting_task_log() entries are not deleted when task is.
• #1348338: Fixed Ajax requests ignore base_url() setting - followup.
• #1437856: Fixed Display of Client Quota missing pager navigation bar
• #1388542: Fixed packages in sites/all/modules should override profile/*/modules
• #1498102: Fixed Dates and times are incorrect on freshly created tasks
• #1472480: Fixed Restrict the Task Queue to one task per site each cron run
• #1493286: Fixed SSL certificates not being created
• #1485746: Fixed MySQL root password incorrectly escaped in frontend
• #1528996: Nginx microcaching should use fastcgi_cache_valid with 1s only for upstream errors
• #1472460: Nginx configuration denies HTTP request methods: PUT, DELETE and OPTIONS and it breaks services/REST
• #1534306: Duplicate directives in the Nginx config cause issues with recommended Dotdeb Nginx build
• #1528996: Nginx microcaching shouldn't cache any upstream errors
• #1524860: Empty response 444 in Nginx confuses search bots
• #1515762: Nginx microcaching should skip all known AJAX requests
• #1505370: Conflict between Mime Type and Document Type in Nginx
• #1498774: Set higher value for map_hash_bucket_size in Nginx by default
• #1283854: Fixed Use of parameters in provision_file()->symlink() is incorrect
• #1387394: Fixed deleting a site doesn't delete soft links
• #1388542: Fixed packages in sites/all/modules should override profile/*/modules
• #1486298: Fixed End of install process is messy
• #1478984: Add Access-Control-Allow-Origin header with wildcard for static files in Nginx, also to support cdn-delivered @font-face

5. Known issues

No know issues at this time.

The Aegir team is proud to announce the seventh release in the stable 1.x release branch!

This release ships various bugfixes that have accumulated in the issue queue since the 1.6 release, including a lot of fixes on Nginx support. We also ship a new clustering module aimed at lightweight slave deployments named the pack module, designed to replace the cluster module which has performance and configuration issues.

Also note that 2.x development is moving ahead with Drush 5 and Drupal 7 support, along with code refactoring and other features. Debian package builds will be available shortly in a separate Debian repository.

We also want to take this opportunity to welcome to our core team omega8cc, a long time contributor that will now be responsible for the maintenance of the Nginx code. Welcome on board Grace!

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 releases prior to 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!

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 :)

3. Features

• #1463494: Radioactivity does not work with Nginx configuration
• #1353608: ad module incompatible with current nginx_simple_include.conf settings
• #1259098: nginx HTTP service should support different restart commands
• #1171508: Nginx capabilities detection is not reliable
• #1408410: Add microcaching to Nginx config by default
• #1062168: chained certificates support

4. Bug fixes

• #1439196: Don't lock the DB during backups
• #1442906: Nginx does not listen on all supplied IP addresses
• #962044: Fixing broken Boost support for the home/root location in Nginx #104004
• #1388906: It is possible to break Nginx based install with upload progress by enabling nginx_ssl feature
• #1346712: Nginx config files required as includes in vhosts are not copied when Nginx SSL feature is enabled
• #1444172: Syntax error in the help description of provision-login_reset
• #1346794: Nginx SSL declarations need to be added to redirect vhosts
• #1450134: aliases are not validated in the validate step
• #1435340: node param "created" is refreshed on node_save
• #1421356: Wrong variables for files paths hardcoded for D7 sites
• #1369608: Provision shoudl add extra config for nginx ssl hosts
• #1437386: Notices from hosting_package.module
• #1018596: Aegir forms don't work in MSIE 8.0 (?)
• #1405380: drushrc file permissions are set to 0400, perhaps should be 0440
• #1396326: Mod rewrite double escapes URLs
• #1359258: Broken DB URL when installing 1.6
• #1202960: Aegir Install Script Not Picking up db information from $_SERVER

5. Known issues

• #1493286: SSL certificates not being created
• #1498774: Nginx version 0.7.66 or newer is required

The Aegir team is happy to release the seventh stable release in the 1.x branch.

This release fixes a regression introduced in the 1.5 release that stopped users from being able to compare sites when migrating. It also contains a number of small bug fixes and documentation fixes.

We recommend you upgrade your Aegir system.

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 releases prior to 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!

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 :)

3. Bugfixes

• #1333978: add a conditional when validating site aliases to ensure that not only do no other sites use this alias, but that it isn't identical to the site name itself. Fixes a redirect loop
• #1330984: by Steven Jones: Fixed Long list of notices on site verify.
• #1330018: by Dane Powell: Fixed Can't compare platforms ('table doesn't exist' and other warnings).
• #1146238: by mig5: Fixed The Reset password task for Drupal 5.x sites creates not working one-time login link.
• #1322208: by helmo - fix provision-restore help information and add an example
• #1336838: Added documentation for --makefile to provision-save, and fixed the style.

4. Known issues

See also the 1.0 release notes for known issues in the 1.x series.

The Aegir team is happy to release the sixth stable release in the 1.x branch.

This release fixes not being able to install Drupal 7.8 sites on PHP 5.2, an issue causing automatic installations to fail and other minor fixes.

We recommend you upgrade your Aegir system.

1. Another special note for users of the Debian packages

We've moved the location of the Aegir packages, so you must update your apt configuration. Further details can be found the in original announcement of this change: Debian archive migrated to debian.aegirproject.org.

The Debian packages also install Drush Make using a package rather than a manual download. If upgrading, you may be prompted to remove your current installation of Drush Make to continue.

2. 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 releases prior to 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!

3. Need help?