2.0-beta1 release [#2014053]

So what's missing for a beta release? any critical functionality we're waiting on?

should we wait for subdir support? (#705026: Allow creation of example.com/foo and example.com/bar type of sites (Part I))

i'd keep a freeze exception for that functionality and go ahead with that beta1 release.

Draft release notes...

* feature freeze, exceptions may be granted on a case by case basis
* will run in production at Koumbit soon
* next step: tackle RC bugs

debian/changelog says:

  * Feature freeze begins, only critical and major bug fixes will be
    committed.
  * A few bugfixes, especially to the Debian package, the new views code
    and nginx support.
  * This release adds subdirectory support, a nice homepage and fixes SSL
    support and IP allocation on clusters. We also ship with a wider
    variety of roles.

New features

Support for installing in subdirectories (#705026: Allow creation of example.com/foo and example.com/bar type of sites (Part I))
proper homepage on startup so non-logged-in users don't see an error page, and new users have basic instructions (#1793740: Default home page for aegir is a 403)
SSL support for clusters should now work properly (#2000964: Install of web pack with ssl fails to allocate IP and cert)
New roles added: 'aegir platform manager', 'aegir administrator' (#1403208: Add additional roles)

Bug fixes

#2005698: Invalid argument supplied for foreach() Service.php:144
#1972286: Unknown options for provision-save
#2013683: IP addresses break Aegir login, cookies
#1997088: Views filter for status does not tell what to filter for.
#1876350: Convert list of platforms to use views
multiple files can be managed in a single context now (see #2000038: cannot generate multiple configuration files in nginx, #1784108: pack (and cluster?) modules incompatible with SSL)
nginx cloaks database credentials properly now
#1635622: default nginx config doesn't talk to the default php-fpm config in Debian Wheezy and sid
lots of fixes for the Debian package, including

Known issues

These are related to drush:

* #1931000: Missing drush backend output in frontend log / #1982502: Reduce complexity of backend invoke; consider removing concurrency
* #1991764: Support using a distribution as core

These are follow-up issues for subdirs:

Comments

Comment #1

ergonlogic

he/him

English

Montréal, Québec 🇨🇦

commented 6 June 2013 at 20:50

To justify a freeze exception: we have a working subdir feature in the 'subfolders' branch, and a detailed plan to re-implement it better. The front-end of that re-implementation is mostly done, in the 'subdirs' branch. Once we get the proper service/context/config classes in place, the rest should be pretty straight-forward. Also, this will remain an 'experimental' feature for the 2.x cycle.

Comment #2

steven jones commented 7 June 2013 at 06:11

We should probably wait for another stable version of Drush? Or recommend the dev version right? Because of #1982502: Reduce complexity of backend invoke; consider removing concurrency Aegir might not pick up all errors with lower versions of Drush.

Comment #3

ergonlogic

he/him

English

Montréal, Québec 🇨🇦

commented 10 June 2013 at 14:01

Note that we now have a functioning subdirectory feature. While it could still do with some work, it should be sufficient to include in a beta release, and thus not require a feature freeze exception.

Comment #4

helmo commented 12 June 2013 at 07:46

Version:

7.x-2.x-dev

» 6.x-2.x-dev

Having a new drush release would be nice... but lets not wait too long just for that.

Comment #5

anarcat commented 14 June 2013 at 19:19

alright, i asked around for a 5.10 drush release, but no answer, so i'll go ahead with the beta anyways and just mention those as known issues in the relnotes.

i'll try to push the release as much as possible today, but i leave in 2h so that may be a little tight.