Assert keyName not null and not undefined in get() and set()
Remove unnecessary require
Remove unused variables
Remove unnecessary comment
because http://discuss.emberjs.com/t/documentation-needs-api-is-it-only-for-singleton-controllers/911/3
Merge pull request #2797 from tricknotes/remove-unnecessary-require

Remove unnecessary require
Merge pull request #2798 from tricknotes/remove-unused

Remove unused
Fix naming of _displayPropertyDidChange in comment
Merge pull request #2802 from ghedamat/rename-display-property-did-change

Fix naming of _displayPropertyDidChange in comment
Merge pull request #2800 from gilesbowkett/document-needs-only-for-singletons

document that 'needs' is for singleton controllers only
Clarify subclasses of Ember.CoreView #2556
Fix typo in array mixin docs
Merge pull request #2806 from javierav/fix-docs

Fix typo in array mixin docs
Moved set of events to listen on by default to a property of EventDispatcher so it can be overridden
visit helper update router url before handling it
Merge pull request #2818 from teddyzeenny/visit-url

visit helper should update router url before handling it
Merge pull request #2805 from pootsbook/master

Begin Documenting Ember.CoreView
Merge pull request #2796 from uzzz/master

Assert null and undefined keyName in get() and set()
bump ember-dev

- rake test now no longer leaks child processes when something goes wrong.
- rake test now uses a less common port for serving the assets.
- rake test's asset server's port is now configurable via TEST_SERVER_PORT
Utilize the browser console.assert when possible

Currently our asserts are catchable by try/catches.
This can occur accidentally, hiding real issues in 
both user code, framework code, and explicitly in
promises.

Chrome's currently implementation of console.assert
is not catchable, and does not interfere with the
programs execution. This is likely how we should model
our assert system.