Release 0.30

[crowbot]

Before release candidate date

• [x] Deprecate purge request https://github.com/mysociety/alaveteli/pull/4252
• [x] Update model annotations https://github.com/mysociety/alaveteli/pull/4233
• [x] Remove deprecated code scheduled for removal in this release https://github.com/mysociety/alaveteli/pull/4234
• [x] Add a description of the release to the Changes file in the release branch
  • [x] Migrations?
  • [x] commonlib
  • [x] Template changes
  • [x] Anything else?
• [x] Pick a date for the release branch to be cut ("release candidate date")
• [x] Make an announcement to the translators that they should ensure they have any pending translations saved in Transifex
• [x] Add Houdini to core https://github.com/mysociety/alaveteli/pull/4249
• [x] Update alavetelitheme https://github.com/mysociety/alavetelitheme/pull/99
• [x] Update WDTKtheme https://github.com/mysociety/whatdotheyknow-theme/pull/423 and https://github.com/mysociety/whatdotheyknow-theme/pull/424
• [x] Remove user.admin_level https://github.com/mysociety/alaveteli/pull/4251
• [x] Remove obsolete partials https://github.com/mysociety/alaveteli/pull/4250

On release candidate date

~- [ ] Update newrelic https://github.com/mysociety/alaveteli/pull/4257~ doesn't support ruby 1.9

• [x] Test supported operating systems to make sure there haven't been dependency/install regressions
  • [x] Wheezy
  • [x] Precise
  • [x] Jessie
  • [x] Trusty
• [x] Commit translations to a hotfix
• [x] Update and commit the translations
• [x] Run brakeman #4276 #4277
• [x] Test/fix the release
• [x] Send a message to the dev group
• [x] Make sure that all dependent themes have develop branches that are compatible with the release branch
• [x] Send a message to the designers to review how design changes have integrated
• [x] Fix any issues reported by testers & designers

On the release date

• [x] Download and commit all the current translations to the current release branch
• [x] Check doc/CHANGES.md is up to date with any fixes made on the release branch.
• [x] Update the current version in doc/CHANGES.md
• [x] Update the ALAVETELI_VERSION constant in the release branch (config/initializers/alaveteli.rb).
• [x] Merge the release branch into master
• [x] Merge the release back into the develop and wdtk branches
• [x] Make sure that all dependent themes (alavetelitheme, whatdotheyknow-theme) have master branches that are compatible with the release branch
• [x] Tag all the dependent themes with a use-with-alaveteli-x.x.x tag
• [x] Send a message to the dev group with a link to the Changes file
• [x] Delete any topic branches that have been now merged to master (find candidates with git branch --merged master)
• [x] Add the release details to the GitHub releases page
• [x] ~Tweet and/or blog about the new release!~ Put it in the community update.

[crowbot]

We should do #3805

[crowbot]

We should do https://github.com/mysociety/alaveteli-professional/issues/314