Ember.Select shouldn't trigger change for when content is an empty array-like obejct
The previous check for triggering when content was empty relied on
the falsiness of `[]` but would incorrectly trigger change when the
content was an Array-like object whose proxied `length` was 0.

Specifically this would cause issues with setting the `contentBinding`
of a Select to the `DS.Model.find` values that are empty initially
setting the Select's `selection` from whatever the current value is to
`undefined` when change was triggered on an empty content.

Asynchronously, data would return and the content would become populated
but the selection value had already been unset.
Add concatenatedProperties documentation
Merge pull request #1653 from lukemelia/concatenated-properties-doc-edit

Add concatenatedProperties documentation

Fixes #1627, Fixes #1652. Thanks, @javierav
Remove redundant calls to ComputedProperty#property()
Fix default `into` for nested routes

By default, routes now render into their nearest
parent that rendered a template.

As a side-effect, application is now even less
special. It just happens to be a top-level route,
like `loading`.
Support camelized or underscored template names
Merge pull request #1654 from elucid/redundant-property-calls

Remove redundant calls to ComputedProperty#property()
bugfix Ember.Set#addEach documentation
Merge pull request #1655 from javierav/docsfix

syntax highlighting for Ember.Set#addEach documentation
Updated QUnit to @wagenet's fork to fix IE issue
Use Ember.Error instead of default
Fix IE whitespace issues in tests
More robust XSS tests
Normalize urls in tests for IE
Fix object comparisons in IE tests
Fix tests with same names
Fix build order for old-router
Update route-recognizer with wildcard fixes
Add back old template lookup logic to Ember.View for when containers are not available (old-router)
Make outlets work inside block helpers