Add rake test description

No behavior change
cache_key consults updated_on timestamp if present

- Extract max timestamp retrieval for cache_key
- Update changelog for cache_key changes
change log4r link to most recent, updated location
fix broken links to README docs in intro
Allow use of assert_template with the :file option.
This worked in Rails 3.2, but was a regression in 4.0.0.beta1
Clarified need to remove existing code in welcome index.

Signed-off-by: Chelsea Macaluso <c.macaluso@modcloth.com>
Clarified removal of public/index.html file

Signed-off-by: Trent Michaels <t.michaels@modcloth.com>
Fixed grammatical error and simplified paragraph concerning controllers.

Signed-off-by: Chelsea Macaluso <c.macaluso@modcloth.com>
Reverting commit regarding public/index.html (no longer in Rails 4.)

This reverts commit f8461f73c77c186ad0aa735fe9877990bffe1990.
Add explanation of :dependent => :restrict

Based on information here: http://api.rubyonrails.org/classes/ActiveRecord/Associations/ClassMethods.html#method-i-has_many
integrate the strong params README into the AC guide.

The current ActionController guide does not mention strong parameters
at all. I integrated the README into the guide to explain the API.

I also included a section to illustrate that the API does not solve
all possible whitelisting scenarios.

The origin was #9454.
Merge pull request #9465 from senny/document_strong_params_in_ac_guide

integrate the strong params README into the AC guide.
fix the sql that is generated from scoping
More helpful error message when instantiating an abstract class

Calling a literal ActiveRecord::Base.new raises NoMethodError,
since it ends up calling Class.abstract_class? which does not exist.
Similarly, instantiating an actual abstract class hits the database,
when conventionally it should immediately throw NotImplementedError.

ActiveRecord::Base can't be made abstract without breaking many,
many things, so check for it separately.
Use custom visitor class for optimized url helpers

Rather than trying to use gsub to remove the optional route segments,
which will fail with nested optional segments, use a custom visitor
class that returns a empty string for group nodes.

Closes #9524
Bring config.allow_concurrency back

Since the Rack::Lock still exists in development,
let's provide a way to disable it explicitly.
Created an unscope method for removing relations from a chain of
relations. Specific where values can be unscoped, and the unscope method
still works when relations are merged or combined.
Merge pull request #9532 from neerajdotname/fix-sql-in-example

In example fix sql that is generated from scoping
Merge pull request #9200 from wangjohn/unscoping_activerecord_merging

Introduce relation #unscope
Small Typo