This reverts commit 3eef1c7c.
The css compressor should be set in sass-rails plugin. Check
https://github.com/rails/sass-rails/commit/339529f9f6433047df6358c0439e6641cb74f045
for the fix.

With the new sprockets-rails we need to explicitly set the CSS
compressor.

See https://github.com/rails/sprockets-rails#changes-from-rails-3x

Custom dependency trackers for the template digestor

Improve `rake stats` for JavaScript and CoffeeScript

Ignore block comments and calculates number of functions.

Some minor AR changelog modifications [ci skip]

Added documentation to touch throwing an error

Keep second fraction when DateTime#change is called.

update 4.0 release notes to reflect the removal of auto explain.

Changed update to use prepared statements

to use it on an unpersisted object.

Raising an ActiveRecordError when one tries to use touch on a new record object

object that has not yet been persisted. This behavior follows the
precedent set by update_columns.

This reverts commit 046e27a7.
Check https://github.com/rails/rails/pull/8815#issuecomment-14026122 for
details.

AS JSON encoder: remove monkey patch of Array

Added `ActiveSupport::TimeWithZone#to_r` for `Time#at` compatibility.

Closes #9404

Taking the wise advice of @carlosantoniodasilva

don't apply invalid ordering when preloading hmt associations.

closes #8663.

When preloading a hmt association there two possible scenarios:

1.) preload with 2 queries: first hm association, then hmt with id IN ()
2.) preload with join: hmt association is loaded with a join on the hm association

The bug was happening in scenario 1.) with a normal order clause on the hmt association.
The ordering was also applied when loading the hm association, which resulted in the error.

This patch only applies the ordering the the hm-relation if we are performing a join (2).
Otherwise the order will only appear in the second query (1).

update the example for `after_commit` in the guides.

This is a follow up to #9356.

Remove `--builder` option from `rails` command

Ability to use a custom builder by passing `--builder` (or `-b`) has
been removed. Consider using application template instead. See this
guide for more detail:
http://guides.rubyonrails.org/rails_application_templates.html

remove config.auto_explain_threshold_in_seconds

We discussed that the auto explain feature is rarely used.
This PR removes only the automatic explain. You can still display
the explain output for any given relation using `ActiveRecord::Relation#explain`.

As a side-effect this should also fix the connection problem during
asset compilation (#9385). The auto explain initializer in the `ActiveRecord::Railtie`
forced a connection.

Updated doc to clarify about update_all and delete_all

[ci skip]

Point to the Protected Attributes gem to those who want a smoothly
upgrade path before to change to use Strong Parameters.

[ci skip]