[BUGFIX beta] preserve base URL when using history location for routing
[DOC beta] Document Ember.Route #controllerName and #viewName properties.
[FEATURE query-params-new] Query Parmas support arrays
[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
```
Merge pull request #4067 from raytiley/qp-array

[FEATURE query-params-new]Support for Arrays
[FEATURE query-params-new] Support push/pop of arrays
Revert "[FEATURE query-params-new] Support push/pop of arrays"

This reverts commit ce61a329404672a7d53039c2374187d8c4830a66.
[FEATURE query-params-new] Fix array comparison issue
Merge pull request #4069 from machty/qp-broken-build-fix

[FEATURE query-params-new] properly handle array observer
[BUGFIX] Deprecate manually assigned templates for Components.

In most circumstances a Component does not have a template or
templateName property. In a component the block passed when calling it
(in a handlebars template) is interpreted as its template, and a
template that was registered as `components/my-component` becomes its
layout. This was recently fixed in 1.2.0 (with the
`container-renderables` feature), but many applications already existed
that manually register their components (via `Ember.Handlebars.helper`).

This change allows usage of `template` and `templateName` properties on
a component, but generates a deprecation warning if you do so.
Merge pull request #3900 from rjackson/fix_manually_registered_components

[BUGFIX] Deprecate manually assigned templates for Components.
[DOC] Add docs for Route#refresh
Merge pull request #4074 from machty/refresh-docs

[DOC] Add docs for Route#refresh
[DOC] Move docs on built in Route actions back into the Route documentation
[BUGFIX] sync router.js: es3-safe `promise.catch()`
Merge pull request #4075 from bmac/move-built-in-actions-back-to-route

Move docs on built in Route actions back into the Route documentation
Merge pull request #4077 from machty/es3-catch

[BUGFIX] sync router.js: es3-safe `promise.catch()`
[DOC][BETA] Improve Em.computed.notEmpty docs to note using array syntax for arrays
[BUGFIX beta] Allow Component to lookup a templateName if specified.

Prior to this change, specifying `templateName` to a component would not
cause that template to be used (since we were overriding the
`Ember.View.template` function with `null`).

This change uses the logic from `Ember.View.template`, which is not
ideal, but I think that these custom docs are pretty important to have.
(They help instruct users that the block passed to a component is
interpreted as its template.)
Merge pull request #4081 from alexspeller/improve-notempty-docs

Improve Em.computed.notEmpty docs to note using array syntax for arrays