Depend on rails-4.0.0, and get the bundle installing.
Add TODO about migrating from attr_accessible to Strong Parameters.
Update config files for rails-4.0.0.rc2.
Add gem to work around Rails 4's deprecation of observers.
ActiveRecord 4 expects 'scope' to be given a callable object.
Rails 4 doesn't allow method-indiscriminate route matching.
Fix that state machine's initial state was not set.
Generate binstubs for rspec-core.
New 'find_or_create_by' syntax.
Update schema.rb with Rails 4/Ruby 1.9 syntax.
Use boolean Active Record type for Clause's 'boolean_value'.

In Rails 3, a call like:

Clause.create!(:name => 'foo', :boolean_value => false)

set the 'boolean_value' column to 0. But in Rails 4, the value for
'boolean_value' is silently thrown away; the 'boolean_value'
column is left set to NULL.

Fix this by using Active Record's 'boolean' data type, and being
a little more explicit about getting and setting the 'boolean_value'
attribute.
Remove use of deprecated Relation#all.
Guard against new, unpersisted records appearing in the timeline.

After upgrade to Rails 4, calling co.proposals in one_click#dashboard
began to return an array containing a new, unpersisted Proposal. This
caused errors when trying to display it, as required attributes were
nil.
Don't error if a timeline event has no timestamp.
'Invitations' request spec: PUT method is now PATCH.
Short-circuit STI explicitly instead of using abstract_class.

Classes like FoundingMember (a descendent of Member) exist only to
allow convenient syntax like FoundingMember.new. It's not intended
for the 'type' column' to ever contain 'FoundingMember'; it should
just have 'Member.

Previously, we achieved this by setting 'abstract_class' true for
these convenience subclasses. This causes the class to be ignored
by Rails' STI machinery when calculating what should go in the
'type' column.

In Rails 4, abstract classes are not allowed to be instantiated.
So we have stopped making these abstract classes, and instead
tell Active Record explicitly what to put in the 'type' column for
these classes, by using the 'sti_name' method.
Add dummy view template so that mailer spec doesn't fail.
Ensure install_organisation_resolver reopens ApplicationController.

The spec support file install_organisation_resolver.rb is supposed
to add methods to the existing ApplicationController.

Under Rails 4 (or possibly the more recent rspec-rails we're using),
this file caused ApplicationController to be entirely redefined,
resulting in NoMethodErrors on 'current_user', etc..

Make sure this doesn't happen by explicitly requiring
app/controllers/application_controller first.
Stop Rails complaining about unspecified handler in stubbed template.
Update PUT to PATCH in member resignation flow.