Add failing test for hasMany relationships

If adapter does not return any data for a hasMany relationship,
the unsaved hasMany records disappear from the relationship.
Fixes #1466
Always keep the hasMany around when payload arrives

We should always keep the current hasMany value if the payload
has no relationships with that key
Docs use model on controller instead of route

Changed the documentation so that the model property referenced is on
the controller of the route rather than the route itself. Since the
route already has a method called model, referencing the model property
as an Ember-Data model can be confusing.
Publish to canary branch of components/ember-data repo.
Update store docs from old style adapter specification
Merge pull request #2069 from alexspeller/fix-store-docs

Update store docs from old style adapter specification
Add token.
Update version calculation to match Ember.js.
Remove Makefile.
Merge branch 'merge-2064'
Migrate s3 publishing to ember publisher
Merge pull request #2071 from rondale-sc/migrate_s3_publishing_to_ember_publisher

Migrate s3 publishing to ember publisher
[Fix] Add extension to publish-build ( publish_to_s3 ->
publish_to_s3.js )
Merge pull request #2072 from rondale-sc/bugfix-add-extension-to-publish-build

[Fix] Add extension to publish-build npm script
 Bump to fixed ember publisher version
Merge pull request #2073 from rondale-sc/bump-ember-publisher-version

 Bump to fixed ember publisher version
Merge pull request #2046 from gbabiars/update-model-docs

Docs use model on controller instead of route
Merge pull request #1975 from emberjs/1467Fix

Ensure hasMany records are kept when adapter returns no relationship data