Ember.Select shouldn't trigger change for when content is an empty array-like obejct
The previous check for triggering when content was empty relied on
the falsiness of `[]` but would incorrectly trigger change when the
content was an Array-like object whose proxied `length` was 0.

Specifically this would cause issues with setting the `contentBinding`
of a Select to the `DS.Model.find` values that are empty initially
setting the Select's `selection` from whatever the current value is to
`undefined` when change was triggered on an empty content.

Asynchronously, data would return and the content would become populated
but the selection value had already been unset.
Add back old template lookup logic to Ember.View for when containers are not available (old-router)
Add test for #1669
Fix Chrome (pre v25) MutationObserver Memory Leak

https://github.com/tildeio/rsvp.js/pull/40
https://github.com/emberjs/ember.js/issues/1667
http://code.google.com/p/chromium/issues/detail?id=160985
Fix typos in documentation guidelines
Add title attribute binding to linkTo helper.
Adding unit test for nested outlets
Merge pull request #1675 from stefanpenner/fix_rsvp_memory_leak

Fix Chrome (pre v25) MutationObserver Memory Leak
Merge pull request #1676 from bobey/master

Add title attribute binding to linkTo helper
Don't clobber rootURL with undefined
Merge pull request #1669 from go1dfish/old-router-view-templatefromname

Add back old template lookup logic to Ember.View for old-router
missing this in SortableMixin#contentArrayDidChange causes observers not to be properly removed
Removes tabs controls

They've been deprecated for a while and I haven't noticed an outcry.
Merge pull request #1683 from trek/remove-tabs-control

Removes tabs controls
App.container was not meant to be a public API

It appears that people are starting to use
App.container.lookup as the public API for
globally getting other controllers outside of the
router or other controllers.

This was not intended to be a public API.

Instead, you should trigger events on a route
(or a parent route), which have access to
`this.controllerFor`.

Example:

    App.ApplicationRoute.extend({
      events: {
        search: function(term) {
          this.controllerFor('search')
            .set('term', term);
        }
      }
    });

    App.SearchField = Ember.TextField.extend({
      insertNewline: function() {
        var term = this.get('value'),
            controller = this.get('controller');

        controller.send('search', term);
        this.set('value', '');
      }
    });

Events sent to the controller will bubble up to
the current route, and then up the route hierarchy
Provide a precompilation package

This should make it easier to maintain external
precompilers without stubbing out parts of Ember
Correct spelling of 'already' in assertion.
Merge pull request #1686 from topfunky/spelling/already

Correct spelling of 'already' in assertion.
More useful debug name for generated controllers
BREAKING CHANGE to router events signature

Previously, the router events received this
signature:

    edit: function(handler, context) {
      // `this` is the events hash
    }

It now receives:

    edit: function(...args) {
      // `this` is the route handler
    }