collection view will now defer all normalization to the resolver
fix typo and remove commented out assertion
[FEATURE propertyBraceExpansion]

Add support for brace-expansion in dependent keys, observer and watch
properties.  The complete list of methods with this support is as follows:
- computed
- reduceComputed
- addObserver
- removeObserver
- addBeforeObserver
- removeBeforeObserver
- watch
- unwatch

This is most useful with array computed properties, although it is supported in
other cases.

Example:
```js
// The following two are equivalent
Em.O({
  filtered: Em.computed.filter('list.@each.propA', filterFn).property('list.@each.propB')
});

Em.O({
  filtered: Em.computed.filter('list.@each.{propA,propB}', filterFn)
});

// The following two are equivalent
obj = {};
observer = function() {};
Ember.addObserver(obj, 'foo', observer);
Ember.addObserver(obj, 'bar', observer);

Ember.addobserver(obj, '{foo,bar}', observer);
```
[BUGFIX beta] Allow a reduceComputed to have an undefined initialValue.

- Stop `ReduceComputedProperty.prototype.initialValue` from asserting
  that a reduce computed's initialValue must not be undefined.
- Modify `Ember.reduceComputed`'s assertion that initialValue be present
  to check that the initialValue is in options instead of isNone.
- Add a test that relies on an undefined initialValue to pass.
- Add a test that an error is thrown when you define a reduceComputed
  without an initialValue property.
[BUGFIX beta] Fix evaluateUnboundHelper properties
[BUGFIX beta] Soft-deprecate mixed binding syntax in view helper

Someone on IRC got bit by 97dc83b4a5f869c9f86fe8144d4faf168ca41a50,
and I'm sure there will be others, due to doing something like
{{view Ember.View somethingBinding=unquotedPropertyPath}}, which
with the above commit create a binding on the view object
from `somethingBinding`=>`unquotedPropertyPath`, vs. the
(incorrectly but understandably) expected 
`something`=>`unquotedPropertyPath`. This commit will support
the mixed syntax for now but warn the user about it.
Fix another IE test issue - Issue #3525
Added support for jQuery as a `require` module
Should not reference global `Handlebars` object, use `Ember.Handlebars` instead
Merge pull request #3556 from sebastianseilund/handlebars-no-global

Should not reference global `Handlebars` object, use `Ember.Handlebars` instead
Merge pull request #3555 from sebastianseilund/jquery-require

Added support for jQuery as a `require` module
Refactored promises usage:

1) Used a Promise subclass instead of patching and wrapping all the time
2) Updated RSVP to fix a subclassing bug
3) Updated RSVP to support a unified onerror callback that can be used
   instead of patching the `.then` on promises.
Only catch promise errors after injecting helpers
Ember.Test Helpers no longer need to be chained
fix and simplify concurrent wait calls test
Ember-testing should not cause a test failure  when aborting transitions
Introduce registerAsyncHelper which allows for unchained async helpers

All helpers registered with `Ember.Test.registerAsyncHelper` can be called
without being chained.  These helpers will not run until all previous
async helpers are done.  All async helpers after this helper will not run
until this helper is done.

```javascript

Ember.Test.registerAsyncHelper('clickPost', function(app, title) {
  click('.post-title:contains('+ title +')');
});

//... in your test

visit('/');

clickPost('My Post');

andThen(function() {
  equal(find('h1').text(), 'My Post');
});

```
Comment out unenforceable `run.later` ordering tests

Fixes #3526
Comment out more unenforceable `run.later` tests

Fixes #3522
[BUGFIX beta] Fix IE 6/7 RenderBuffer issue

IE 6/7 has a bug that prevents the 'name' attribute from being properly set on
an 'input' created with 'createElement'. This provides a workaround by using IE
specific `createElement` behavior that allows a tag string to be passed to
`createElement` instead of just a tagName.

Fixes #3525