[BUGFIX beta] When selecting controller for view prioritize controllerName over
controller matching template or route name
[BUGFIX beta] Preserve ability to render alternate controller matching template if
controllerName is specified.

Controller precendence for render is as follows:
* explicitly passed controller always has top precedence
* if name explicitly passed, prioritize name over controllerName
* prioritize controllerName when no explicit name
* fall back on routeName
[BUGFIX beta] Force remove `required` attribute for IE8

In IE8, `elem.prop('required', '')` couldn't remove attribute.
(This problem is occured at `required` only. Other attributes work as our
expectation.)

``` javascript
view.set('required', false);
view.$().get(0).outerHTML; // this includes `required` attribute.
```

To remove attribute, `removeProp` is needed.
Revert #3218, add deprecation notice for global Handlebars lookups.
Close #5088 - Fix usage of document.body.contains, check if browser supports this method(ex. ff 3.6)
Container: calls to lookupFactory only call normalize once

[Fixes #4734]
Merge pull request #5091 from pixelhandler/container-lookupFactory-normalize-once

Container: calls to lookupFactory only call normalize once
Migrate doc generation process to node

This removes the call to bundler during build time, which should
increase the avg speed of builds in travis
Merge pull request #5094 from rondale-sc/migrate_doc_generation_to_node

Migrate doc generation process to node
Update npm run-script to npm run

More commonly used and cleaner/less to type.
Merge pull request #5111 from knownasilya/patch-1

Update npm run-script to npm run
[bugfix] fix hardcoded date in s3publisher test
Merge pull request #5114 from rondale-sc/fix_s3_publisher_test

[bugfix] fix hardcoded date in s3publisher test
Fix {{#with view.foo as bar}}

The `with` helper can correctly bind through the `view` keyword when
it's used like this:

    {{#with view.foo}}

But the binding is broken if you try it like this:

    {{#with view.foo as bar}}

This change fixes it.
Add eventDispatcher.canDispatchToEventManager property
It decides if `event` will be dispatched to view `eventManager` or not.
confirm to guidelines, simplify debugging
improve debugging by not having single expression var statements when initializing
simplify finding tests.

simply:
1. ember server —port 8000
2. navigate to http://127.0.0.1:8000/
3. thats it
Merge pull request #5117 from stefanpenner/master

misc nice things
Merge pull request #5116 from ppcano/can-disable-event-manager

[FEATURE event-dispatcher-can-disable-event-manager] eventDispatcher can disable dispatching events to view `eventManager`