0.28.0.0

Highlighted Features

• Upgrade to Rails 4.0 (Gareth Rees, Louise Crow, Steve Day, Liz Conlan)
• The test-unit gem has been removed from the project's Gemfile.
  Alaveteli has used RSpec to run tests for a long time, but Test::Unit was
  also available. Due to an incompatibility between the two, and a desire to
  support a single environment, this is no longer the case.

Upgrade Notes

• This release upgrades Alaveteli to use Rails 4.0. No public-facing API has
  been changed, but if you have custom theme code you may need to update it for
  Rails 4 compatibility. Follow instructions in the official Rails guide (
  http://guides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-3-2-to-rails-4-0-active-record)
  and review our commits in this release to investigate deprecation warnings.
• You may need to migrate any tests in your theme that were using Test::Unit
  to RSpec.

0.27.1.3

Highlighted Features

• Updated broken nl_BE translation (Gareth Rees)

0.27.1.2

Updated translations from Transifex (Gareth Rees)

0.27.1.1

• Updated translations from Transifex (Liz Conlan)

0.27.1.0

Highlighted Features

• Always send warnings of possible spam activity – configure blocking of spam
  activity with ENABLE_ANTI_SPAM (Gareth Rees)
• Fix downloading request Zips when they're unclassified (Gareth Rees)
• Handle parsing mail server logs when using a smarthost (Gareth Rees)
• Removed a reference to MySociety::Config (Caleb Tutty)
• Hide admin navigation items in request PDF download (Gareth Rees)
• Added a set of rake tasks to provide stats on user signups by email domain
  with the option to ban by domain if required (Liz Conlan)
• Added a data export task to help with research (Alex Parsons)
• Add slightly stricter constraints to InfoRequest summaries to prevent really
  short titles like "re" from being used while still allowing acronyms like
  RNIB through - only affects new requests, pre-existing requests which don't
  meet these new requirements will still be treated as valid (Liz Conlan)
• Make the "Show all attachments" and "Show fewer attachments" links on the
  request page translatable (Liz Conlan)

Upgrade Notes

• The :redact_idhash option of MailServerLog#line has been replaced by the
  :redact option. It will be removed in release 0.29.

0.27.0.4

• Fix a bug that meant a Postgres collation that was not compatible with the
  local database encoding could be chosen (Liz Conlan)

0.26.0.9

• Fix a bug that meant a Postgres collation that was not compatible with the
  local database encoding could be chosen (Liz Conlan)

0.27.0.2

Highlighted Features

• Made script/alert-expiring-embargoes executable (Louise Crow)

0.27.0.1

0.27.0.1

Highlighted Features

• Added some more documentation on the 0.27.0.0 release (Louise Crow)
• Fixed rake temp:populate_request_due_dates to not validate requests
  on saving, or try to populate fields that have already been populated
  (Louise Crow)
• Fixed a typo in the delete-expired-embargoes script

0.27.0.0

0.27.0.0

Highlighted Features

• Time in application time zone is used where appropriate in code, this fixes
  a bug in due date calculation for zones offset from UTC (Louise Crow)
• Prevent long authority names overflowing on statistics page (Gareth Rees)
• Fix css bug which allowed some "visually-hidden" elements to affect page
  length (Liz Conlan)
• Header now contains pull-down menu for user-specific links, which has
  swapped place with the search box (Martin Wright)
• This release rolls out the first implementation of Alaveteli Pro - a service
  for use by journalists and campaigners. Includes ability to embargo requests,
  and dashboard for managing to-do items and requests. This is functionality
  being piloted in the UK and is not yet recommended for use in other locales
  (Steve Day, Martin Wright, Louise Crow)

Upgrade Notes

• You can run this release without using the Alaveteli Pro functionality - by
  default it is switched off.

• Please update any overriden templates and theme code that reference times and
  dates to reference the local time zone where appropriate. e.g.

  Time.now => Time.zone.now
  Date.today => Date.current
  DateTime.parse => Time.zone.parse

  See https://robots.thoughtbot.com/its-about-time-zones for a description of
  how Rails handles time zones

• To store the significant dates for requests in the database, you must run
  bundle exec rake temp:populate_request_due_dates after deployment.

• To store events identifying at what point requests became overdue and very
  overdue, you must run bundle exec rake temp:backload_overdue_info_request_events
  and bundle exec rake temp:backload_very_overdue_info_request_events.

• There are some database structure updates so remember to rake db:migrate