[DOC beta] Document Ember.Route #controllerName and #viewName properties.
[BUGFIX beta] Remove false attribute from Ember.View

In IE8 (or older), `jQuery.fn.prop` always update DOM against our
expectation.(This is a jQuery bug but it couldn't fix)
ref: http://bugs.jquery.com/ticket/13558

So the following test is failed due to `view.$().attr('foo')` returns `"false"`.:
* https://github.com/emberjs/ember.js/blob/a449d445/packages/ember-views/tests/views/view/attribute_bindings_test.js#L126

To avoid this issue, `removeAttr` should be called when `null`, `undefined` or `false` is given as value.

But this way contains incompatible changes:

Before:
``` javascript
view.set('checked', false);
view.$().prop('checked'); //=> false
```

After:
``` javascript
view.set('checked', false);
view.$().prop('checked'); //=> undefined
```
Don't call toString at extend time

Doing so will memoize the function so that any Ember.View subclass will return the same value for toString.
[BUGFIX beta] Allow Ember.computed.sort to use property paths in sortDefinitions.

'Ember.computed.sort' 'works only if sortDefinitions contain simple properties.
It will fail if a `sortDefinition` contains a property path (i.e. something
like `person.name`).

A `SearchProxy` is used to shadow the new value of an underlying property with
the old value to ensure proper comparisons take place while searching for an
item in the sorted array. When using a property path rather than a simple
property to sort on, `SearchProxy` will use the actual property path in its
attempt to shadow underlying properties - something like: `{ person.name: 'John
Doe' }`. This causes things to blow up because every comparison between an
existing item `get(itemA, sortProperty)` and a SearchProxy `get(itemB,
sortProperty)` will return a bogus result. In this case, `get(itemB,
'person.name')` will not return the shadowed value (stored as `{ person.name:
'John Doe' } `) but rather the current value of that path on the proxy's
underlying `content`.

This commit allows a proper comparison to take place when a sortDefinition
contains a property path.
[Bugfix beta] improve action without actions hash deprecation warning
[FEATURE ember-eager-update-url] Eagerly update link-to urls

Previously, the url in the address bar would only update
at the very end up the transition. This change causes the
url update to happen immediately unless the transition
was aborted/redirected within the same run loop, which
provides for a better UX 99% of the time.
Merge pull request #4122 from machty/eager-url-update

[FEATURE ember-eager-update-url] Eagerly update link-to urls
Remove a .swp file
Update ember-dev
Use expectAssertion instead of manual assert stubbing
Introduce expectDeprecation. Remove TESTING_DEPRECATION.
[BUGFIX release] We don't need to call didChange after we've copied
[BUGFIX beta] Silently fail when disconnecting from an inactive view
[FEATURE ember-eager-update-url] tweak for hash location

Need to strip hash before eagerly updating url.
[FEATURE query-params-new] active support for numbers and arrays

This should fix  #4118. QPs always get interpreted fromt the URL as
strings. This commit updates router.js so its supports numeric and
array QP when determining active state.

This commit also depends on https://github.com/tildeio/router.js/pull/75
Merge pull request #4126 from raytiley/number-qp

[FEATURE query-params-new] Coerce numeric QPs to strings
Add documentation for Ember.EnumerableUtils.
[BUGFIX beta] fix stripping trailing slashes for * routes

Fixes #3234
Merge pull request #4129 from LevelbossMike/master

Add documentation for Ember.EnumerableUtils.
Merge pull request #4125 from mixonic/disconnect-outlet-without-parent

[BUGFIX beta] Silently fail when disconnecting from an inactive view