Polyfill history.state for non-supporting browsers
simplify history.state support check
warns when trying to get a falsy property
Allows itemView option into the each/collection helper. If itemView
exists and there is a controller container, then it will attempt to
resolve the view via the container.
assert that item view exists in container and camelize lookup name
.jshintrc: set browser:false

Setting `browser:true` predefines a large list of globals. Some of
these, like `window`, `location`, and `setTimeout`, are really useful.
Some of them, like `name` and `event` are really dangerous to have
available as globals. They invite code errors.
Merge pull request #2953 from jamesarosen/james/jshint_browser

.jshintrc: set browser:false
Merge pull request #2887 from gdub22/history-state-polyfill

Polyfill history.state for non-supporting browsers
Remove non ASCII character in handlebars assertion error message

When using the template compiler with certain other tools which do not support unicode, this special character causes a nightmare.
Merge pull request #2954 from Juvenal1228/patch-1

Remove non ASCII character in handlebars assertion error message
Specify controller of a route via controllerName

This commit adds the possibility to specify the controller a route shall
use via a `controllerName` property.

Given the following app:

```
App.Router.map(function() {
  this.resource('team', function() {
    this.route('overview');
    this.route('detail');
  });
});

App.TeamController = Ember.ObjectController.extend({ ... });

App.TeamOverviewRoute = Ember.Route.extend({ controllerName: 'team' });
```

The controller in the `team/overview` template is the `App.TeamController`
instead of the generated `App.TeamOverviewController`. Since the
`controllerName` isn't set on the `App.TeamDetailRoute`, in this
template the generated `App.TeamDetailController` is used.
ember-application test refactoring
fix deprecation warning
add resolveModel to the default resolver
Route#model by default now uses lookupFactory

This makes the default model hook container aware,
utilizing the resolver to locate the model factory
on which to invoke `find`

The original behaviour remains the same, except now
the resolver has the opportunity to easily allow
custom behaviour.
Validate fullNames on resolve

This should both prevent accidental invalid resolutions.

For example prior to this commit, the following would
unexpectedly return the namespace.

```javascript
this.lookupFactory('model:')
```
Merge pull request #2957 from stefanpenner/improve_container

Additional container work and improvements
[fixes #2947] container#unregister
update ember-dev to give proper assertion test failures
Merge pull request #2958 from stefanpenner/improve_container

[fixes #2947] container learns unregister