diff options
author | Seb Bacon <seb.bacon@gmail.com> | 2012-02-07 13:56:07 +0000 |
---|---|---|
committer | Seb Bacon <seb.bacon@gmail.com> | 2012-02-07 13:56:07 +0000 |
commit | 527d1db6f60bfc5bf11578c2305c4698c5f538b7 (patch) | |
tree | da20346b4a185fee69dd22086bda4e14c249dc67 | |
parent | 39b4257ede14af8fd7711fde529372309e17e1d9 (diff) |
changes for version 0.5.1
-rw-r--r-- | doc/CHANGES.md | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/doc/CHANGES.md b/doc/CHANGES.md index d80acec3c..3bc30428e 100644 --- a/doc/CHANGES.md +++ b/doc/CHANGES.md @@ -1,3 +1,31 @@ +# Version 0.5.1 + +## Highlighted features + +This release was mainly to address issue #418, a regression introduced +in 0.5, which was causing deployment problems: + +* Setting `STAGING_SITE: 1` in `general.yml` and running + `script/rails-post-deploy` will ensure the correct behaviour in + production environments +* It should now be safe to run `rake spec` on a production server + +There is one minor new feature in this release: + +* Administrators can follow the auto-login URLs forwarded in emails + from users who want support, and they will remain logged in as + themselves. + +Finally, this release also addresses a number of small bugs, including +the (potentially) important issue #408. + +As usual, there is a [full list of changes on github](https://github.com/sebbacon/alaveteli/issues?milestone=9&state=closed) + +## Upgrade notes + +* On a production server, ensure that `STAGING_SITE` is set to `1`, + and then run `script/rails-post-deploy` as usual. + # Version 0.5 ## Highlighted features |