avoid exception due to console miss on IE 8
Fix code comment typo in Ember.run.bind
Merge pull request #4178 from balinterdi/fix-ember-run-bind-comment-typo

Fix code comment typo in Ember.run.bind
Allow jQuery version 1.11 and 2.1

Both RC1's of jQuery 1.11 and 2.1 have just been released.

(I screwed up last PR)
Merge pull request #4172 from Costent/master

avoid exception due to console miss on IE 8
Merge pull request #4181 from dimitrisuls/patch-1

Allow jQuery version 1.11 and 2.1
Drop file with un-used observer and childContainer cleanup
[FEATURE query-params-new] Only scope conflicting query params
Fix slight documentation typo
Merge pull request #4186 from raytiley/qp-changes

[FEATURE query-params-new] Only scope conflicting query params
Merge pull request #4188 from josepjaume/patch-2

Fix slight documentation typo
Fix a couple of document typos in enumerable
Merge pull request #4184 from mixonic/drop-childContainers

Drop un-used observer and childContainer cleanup
Merge pull request #4191 from fanta/enumarable_typos

[DOC beta] Fix a couple of documentation typos in enumerable
[DOC beta] Document the send method on Ember.ActionHandler
[FEATURE query-params-new] alias computed.reads as computed.oneWay

oneWay is ambiguous. Which way?

Ember.computed.alias is a way more semantically meaningful alias of
Ember.computed.oneWay.

Example: http://jsbin.com/ucanam/3000

Putting this in query params because I'd like to use this
in some of the examples for query params; seems like it'll be
common lightweight pattern for buffering small changes, and
oneWay is just enough of a mental hurdle to necessitate this.
Merge pull request #4112 from machty/computed-reads

[FEATURE query-params-new] alias computed.reads as computed.oneWay
Merge pull request #4192 from bmac/action-handler-send-docs

[DOC beta] Document the send method on Ember.ActionHandler
Update CHANGELOG.md for 1.4.0-beta.3.
[BUGFIX BETA] BREAKING: Fixed how parentController property of an itemController when nested.

When an `itemController` is specified for an ArrayController that itself has a `parentController`
set, the framework was previously setting the itemController's `parentController` property to the
ArrayController's `parentController` instead of the ArrayController itself. This commit fixes that
behavior, and improves the docs, naming, and logic around this case.

If you were relying on an itemController's `parentController` skipping a generation, you will
need to use `parentController.parentController` or better yet, avoid the Law of Demeter
violation and provide a sensible method on the ArrayController that itself delegates to its
`parentController`.