Make explicit that the view file need to be created [ci skip]

Closes #13566
Removed elipsis indicating that the reader should have more code than what is pasted.

[ci skip]
Merge pull request #13557 from gmarik/patch-1

Use `Array#wrap` instead `Array()`
Add CHANGELOG entry for #13557 [ci skip]
Merge pull request #13542 from robin850/issue-13530

Fix enum writers when using integers
Move default production database to URL sub key

By using the URL sub key in the `database.yml` by default we are exposing the ability to set other attributes such as `pool` or `reap_frequency` without need of modifying the URL to contain non-connection specific information.
Downgrade bundler until 1.5.2 is available

Bundler sets the THOR_DEBUG environment variable causing Thor to
re-raise exceptions on exit. This is breaking the railties tests
for generators where we are trying to capture error output.

The PR bundler/bundler#2794 fixes this by adding a per-instance
config `:debug` but this has not been released yet so to prevent
errors going unnoticed downgrade bundler to 1.3.5 until such a
time that 1.5.2 has been released.
Merge pull request #13569 from schneems/schneems/default-url-sub-key

Move default production database to URL sub key
Enable fast_finish in the travis configuration

Since rbx and jruby builds are being allowed to fail lets receive the
build information early enabling this option

See http://about.travis-ci.org/blog/2013-11-27-fast-finishing-builds/
Adding missing require
Reverse 821525e and wrap run_generator call

Ruby 2.1.0 includes the json gem 1.8.1 by default so we need bundler 1.5.1
for `bundle install` to work. To fix this reverse the downgrade to 1.3.5
and wrap the `run_generator` call with a block that resets `THOR_DEBUG`.
Automatically maintain test database schema

* Move check from generated helper to test_help.rb, so that all
  applications can benefit
* Rather than just raising when the test schema has pending migrations,
  try to load in the schema and only raise if there are pending
  migrations afterwards
* Opt out of the check by setting
  config.active_record.maintain_test_schema = false
* Deprecate db:test:* tasks. The test helper is now fully responsible
  for maintaining the test schema, so we don't need rake tasks for this.
  This is also a speed improvement since we're no longer reloading the
  test database on every call to "rake test".
provide correct information [ci skip]
Merge pull request #13528 from jonleighton/maintain_test_schema

Automatically maintain test database schema
Merge pull request #13573 from kuldeepaggarwal/doc-fix-default-values

provide correct information [ci skip]
Use DATABASE_URL by default

See https://github.com/rails/rails/pull/13463#issuecomment-31480799 for full conversation.
Merge pull request #13578 from schneems/schneems/database_url-env-default

Use DATABASE_URL by default
Deprecate unused `symbolized_base_class` and `symbolized_sti_name`.

These methods were only used for the `IdentityMap` which was removed.
They are no longer used internally and should be removed without replacement.

As they were not `:nodoc:`'ed it's better to deprecate them before removal.
Fix documentation for end_year option of date_helper [ci skip]

- While editing an existing record, end_year is equal to current selected year plus 5 by default.
- While editing an existing record, start_year is equal to current selected year value minus 5 by default.
- Fixes #13552

Acked-by: Prathamesh Sonpatki <csonpatki@gmail.com>

Acked-by: Prathamesh Sonpatki <csonpatki@gmail.com>
Building new records with enum scopes now works as expected

Previously, this would give an `ArgumentError`:

   class Issue < ActiveRecord::Base
     enum :status, [:open, :finished]
   end

   Issue.open.build # => ArgumentError: '0' is not a valid status
   Issue.open.create # => ArgumentError: '0' is not a valid status

PR #13542 muted the error, but the issue remains. This commit fixes
the issue by allowing the enum value to be written directly via the
setter:

   Issue.new.status = 0 # This now sets status to :open

Assigning a value directly via the setter like this is not part of the
documented public API, so users should not rely on this behavior.

Closes #13530.