code blocks in which handlebars templates are embedded in <script> tags should be marked as html
{{action}} will target a templates controller

If a function whose name matches an an action is implemented on
a templates controller, that method will be called instead of
delegating the action to the application's current state.

Not sure why a check of `hasOwnProperty` was used, but
it prevented this new behavior from occurring.
Merge pull request #1640 from lukemelia/rebased-pr-1631

{{action}} will target a templates controller. Fixes #1631
YUIDoc fixes
Correct build command

The default rake task is to run the entire test suite. If all we want to do is build that shouldn't be necessary.
make it easier to override controller lookup

Also fix templateName override and activeViews registration

Conflicts:
	packages/ember-routing/lib/system/route.js
{{render}} helper

Conflicts:
	packages/ember-routing/lib/system/route.js
Merge pull request #1645 from bcardarella/patch-1

Correct build command
Merge pull request #1634 from dgeb/html-vs-handlebars-code-blocks

Proper labeling of html vs handlebars code blocks in comments
Merge pull request #1628 from tchak/controllerFor

{{render}} helper and make it easier to override controller lookup
Fix ember-application comments for delaying app init

Remove reference to non-existent `autoinit: false` property passed in to
`Ember.Application.create` and add docs for `deferReadiness` and
`advanceReadiness`
Merge pull request #1647 from jergason/master

Remove references to `autoinit: false` in ember-application
Properly check arguments count for wrapped computed properties.
Fixes #1649.
Fork {{action}} into old and new router flavors
Update {{action}} docs and add some asserts
Eagerly generate toString() of all classes at boot
Add concatenatedProperties documentation
Merge pull request #1653 from lukemelia/concatenated-properties-doc-edit

Add concatenatedProperties documentation

Fixes #1627, Fixes #1652. Thanks, @javierav
Remove redundant calls to ComputedProperty#property()
Fix default `into` for nested routes

By default, routes now render into their nearest
parent that rendered a template.

As a side-effect, application is now even less
special. It just happens to be a top-level route,
like `loading`.