thread_safe is a dependency of active_support
Use thor master to make rails work with Ruby 2.0
All green with Ruby 2.0 :green_heart:
Fix json params parsing regression for non-object JSON content.

Fixes #8845.
Merge pull request #8855 from dylanahsmith/parse-non-object-json-params

Fix json params parsing regression for non-object JSON content.
Merge pull request #8568 from inossidabile/fix-in_clause_length

Correct source for in_clause_length for eager loading (Fix for #8474)
Update guides/source/active_record_basics.md
Merge pull request #8623 from virusman/form_helpers_collectionproxy_fix

Fixed nested fields bug when called with AssociationProxy
Merge pull request #8866 from adomokos/adding_more_tests_to_errors_test

Adding tests to cover untested methods in errors_tests.rb
Merge pull request #8882 from goshakkk/clearer-conditional

Clearer conditional in constraint match check
Add changelog entry for scaffold generator and jbuilder changes

Introduced in 3bfd99defb559af0b017ee920ca714aa1e367fdd.
Related to #8840.

[ci skip]
remove_possible_method -> remove_method

  Date#to_time and Date#xmlschema methods defined in Ruby 1.9.3
Merge pull request #8896 from NARKOZ/patch-5

remove_possible_method -> remove_method
Fix .update_all and .delete_all when using a condition on a joined table
in a default_scope.

`Model.joins(...).where(condition_on_joined_table).update_all` /
`delete_all` worked, but the same operation implemented with a
default_scope generated a SQL error because ActiveRecord ignored the
join but implemented the where condition anyways.
Update engine application layout file path
Fix typo in guides/source/engines.md
Fix typo in guides/source/engines.md
Fix regression introduced in pull request 8812

See https://github.com/rails/rails/pull/8812#commitcomment-2416514
Merge pull request #8907 from rubys/master

Fix regression introduced in pull 8812
Bring back "database already exists" messages when running rake tasks

When running tasks such "rake db:setup", instead of showing messages
like "db_development already exists", it was showing a big stack trace
and a message "Couldn't create database for ..." with the configuration
options, a very confusing message with a big trace.

This brings back the functionality present in 3-2, showing the same
message.