Added method `#eql?` to `ActiveSupport::Duration`, in addition to `#==`.

Currently, the following returns `false`, contrary to expectation:

    1.minute.eql?(1.minute)

Adding method `#eql?` will make this behave like expected. Method `#eql?` is
just a bit stricter than `#==`, as it checks whether the argument is also a
uration. Their parts may be different though.

    1.minute.eql?(60.seconds)  # => true
    1.minute.eql?(60)          # => false
SQLite3Adapter now checks for views in table_exists? fixes: 14041
Propagate test messages through assert_routing helper, Fixes #14908

assert_routing was not raising the message passed into the assertion
violation that it raised. This change propagates messages through
the on_fail error.

This fixes this error:
https://github.com/rails/rails/issues/14908

A test case for this issue is located here.
https://github.com/estsauver/test14908

To see that test case fail in the example app, just run
ruby -Itest test/controllers/guests_controller_test.rb
Updating Associations::Preloader docs

Much of the previous documentation introduced features new in 2011. This
commit refreshes it to provide clearer code examples and spends more
time describing the normal case (preloaded associations) and less time
describing the fallback.

[ci skip]
Roll back open transactions when the running thread is killed.
For now, we will keep sorting the tests.

This reverts commits e969c928463e329fd6529ac59cad96385c538ffb and
bd2b3fbe54e750ba97469a7896e8d143d6dfd465.
world writable might be a bit too open...
Merge pull request #16818 from phoet/patch-4

world writable might be a bit too open...
Fix for inflector's incorrect camelCase replacement for acronyms

Fixes #8015, #9756.

[Fred Wu & Matthew Draper]
Merge pull request #14911 from estsauver/14908

Propagate test messages through assert_routing helper, Fixes #14908
Message doesn't need to be optional
Add test to assert_recognizes with custom message
:scissors:
Added enable_extension! to helper
Do not mark object as persisted after an association is saved

Callback order in Active Record objects are important. Users should not
define callbacks before the association definition or surprising
behaviours like the described at #3798 will happen. This callback order
dependency is documented at https://github.com/rails/rails/blob/31bfcdc77ca0d8cec9b5fe513bdc6f05814dd4f1/activerecord/lib/active_record/associations.rb#L1222-1227.

This reverts #15728.

Fixes #16620.
Remove CHANGELOG entry [ci skip]
Merge pull request #16114 from seuros/test_clean

[Postgresql tests] Added enable_extension! to helper
Add TODO to release the gems before the next Rails release
Use the released jquery-rails gem
Dependencies: bump to jquery-rails 4.0.0.beta2