Rename package to ember-data

[xcambar]

refs #37
Declares the package private so it can not be published to npm (it is already not published).

This allows to use various versions of ember-data easier, most notably with ember-try configs.

[rwjblue]

I do not understand the motivation here, ember-data is already published to NPM and this repo is largely supporting those folks who are still consuming via bower.

Why not just use ember-try to pull ember-data from NPM?

[xcambar]

Using npm, this can be done:

      npm: {
        devDependencies: {
          'ember-data': '#latest', // currently `2.10.0`
          'ember-data': '#beta' // currently `2.11.0-beta.1`
        }
      },

How would I configure ember-data as an npm dep so it fetches the canary channel?
To my knowledge, the same issue will apply after 2.11.0 with the ember-source package, for which the dist-tags are currently { latest: '2.11.0-beta.2', beta: '2.11.0-beta.1' }

Does it help?

[rwjblue]

Canary:

"ember-data": "emberjs/data#master",

Beta:

"ember-data": "emberjs/data#beta",

Release:

"ember-data": "emberjs/data#release",

[rwjblue]

To my knowledge, the same issue will apply after 2.11.0 with the ember-source package

Yes, ember-source will have the issue that you describe (at least at the moment it does). The difference between ember-data and ember-source in this regard is that ember-data is a "normal" addon and it manages its own build at ember-cli app build time, whereas ember-source still relies on pre-built assets. We are working towards fixing this though, and hopefully will have it fixed soonish into the 2.12 beta cycle.

[xcambar]

Thanks for the clarification! Works perfectly!
I'll let you close the PR, in case you'd think there's more to be discussed.