The content property of an ArrayProxy instance should be defined before modifying it
Add hooks to containerView.

It helps in some cases where we need to implement some special behavior
on outlet connection.
We add four new methods to containerView :
`presentCurrentView` and `dismissCurrentView`
`appendCurrentView` and `removeCurrentView`

In cases where we need some special handeling like animations you can
override theus methods

Add willAppear / willDisappear and didAppear / didDisappear

Refactor so it would be easier to override presentCurrentView / dismissCurrentView
Calling removeListener without method should remove all listeners
A listener registered with one can be removed with off
Implements _super() for computed properties
fix api typo and rename findStatesByPath to getStatesInPath

findStatesByPath was incorrectly documented as findStateByPath.
The method has been renamed for consistency with the singular
form getStateByPath, and the code itself has been modified slightly
to be more idiomatic with the rest of the state manager.
Fix for popstate firing on page load.
check if removed observer keeps firing
Don't attempt to concat a concatenatedProperty onto an object that doesn't have a concat method
Remove dependency on `window` throughout Ember

Previously, Ember used the `window` object for
three concerns:

* `imports`: libraries that Ember requires in
  order to work, such as `jQuery`, `Handlebars`,
  and `Metamorph`
* `exports`: the variables that Ember itself
  exports (`Ember` and `Em`)
* `lookup`: the global lookup path for application
  code (e.g. when used in Handlebars templates).

Now, these three concerns are looked up on
`Ember.imports`, `Ember.exports` and
`Ember.lookup` respectively.

For convenience, all three of these are assigned
to `window` by default.

You can change the defaults by assigning a new
Ember object before loading Ember:

```javascript
var imports = {
  Handlebars: Handlebars,
  Metamorph: Metamorph,
  jQuery: jQuery
};

var exports = {}, lookup = {};

Ember = {
  imports: imports,
  exports: exports,
  lookup: lookup
}
```

You can use this to package Ember for external
module loaders like AMD:

```javascript
define("Ember",
  ["exports",
   "App",
   "handlebars",
   "metamorph",
    "jQuery"],
  function(exports, App, Handlebars, Metamorph, jQuery) {
    var imports = {
      Handlebars: Handlebars,
      Metamorph: Metamorph,
      jQuery: jQuery
    };

    var Ember = {
      imports: imports,
      exports: exports,
      lookup: { App: App }
    }

    // distributed ember.js
  });

define("App", [], function() {
  return {};
});

define("Post",
  ["App", "Ember"],
  function(App, Ember) {
    App.Post = Ember.Object.extend({
      // stuff
    });
  });
```

You can use a similar technique to package Ember
Runtime for Node or other environments with
CommonJS-style modules.
Merge pull request #1198 from tchak/container-view-hooks

Container view hooks
Merge pull request #1388 from tchak/events-off

Calling removeListener without method should remove all listeners
Merge pull request #1425 from ghempton/fix-popstate

Fix for popstate firing on page load.
Merge pull request #1440 from lihanli/remove-observer-test

Fix 'removing observer should stop firing' test
Allow extension of chosen prototypes instead of the current all or none.

One of my current projects involves embedding an ember widget into
a rather large pre-existing application   Extending the Array prototype
causes a slew of issues for both first party and third party code
in use on the relevant pages.

This change is backwards compatible and enables, via a new ENV hash,
the ability to choose exactly which prototypes to extend:

window.Env = {
    EXTEND_PROTOTYPES: true,
    PROTOTYPE_EXTENSIONS: {
    //  all: true,
        Function: true,
        String: true,
        Array: true
    }
};

Conflicts:
	packages/ember-metal/lib/core.js
	packages/ember-runtime/lib/ext/function.js
	packages/ember-runtime/lib/system/string.js
Fixed some documentation errors
Allow extension of chosen prototypes instead of the current all or none

One of my current projects involves embedding an ember widget into
a rather large pre-existing application   Extending the Array prototype
causes a slew of issues for both first party and third party code
in use on the relevant pages.

This change is backwards compatible and enables, via updating the
handling of the ENV.EXTEND_PROTOTYPES variable, the ability to choose
exactly which prototypes to extend:

window.Env = {
    EXTEND_PROTOTYPES: {
        Function: true,
        String: true,
        Array: true
    }
};

If window.ENV.EXTEND_PROTOTYPES is true or undefined
Ember.ENV.EXTEND_PROTOTYPES is initialized to the above hash.

If false it is initialized to the above hash with false intead of
true set for each prototype.

Otherwise it is assuemd to be a hash configured properly for the
application at hand.
Merge pull request #1449 from jdsmith2816/prototype-extensions

Allow extension of chosen prototypes instead of the current all or none.
Do not pass jQuery event object if no context is given

As of 19e2631 (merged this Friday), the transition function used by
State.transitionTo passes along a spurious jQuery event object if no
context is given.
Merge pull request #1450 from joliss/transition-to

Do not pass jQuery event object if no context is given