Update dependency to RC6.1 about ember-app-kit

[stefanpenner]

@joefiorini I can(or get someone) add it to our deployment automation tooling. My thoughts are to try and add all these "package management systems" to your deployment flow. We can likely automate most of it.

[joefiorini]

@stefanpenner The more I think about it, I'm wondering if we need the component.js repo. Rather than relying on keeping a third-party repo up-to-date, why not create our own ember-source repo that only contains the latest ember.js and ember-data.js? On every successful build we push to ember-source and keep semver tags for every release. I realize it's duplicating the responsibility of http://builds.emberjs.com, but it would play very nicely with bower, since we can't install from S3. What do you think?

[joefiorini]

Okay, I think I just unknowingly lied a little. Apparently bower DOES pull from S3; setting:

"ember": "http://builds.emberjs.com/ember-latest.js"

actually pulled the latest build and used the e-tag as version string. Interesting. I wonder if that means we could control dependencies by pushing a bower.json to S3 as well?

[rwjblue]

Looks like the components/ember PR was accepted, but it had issues. It required handlebars 1.0.0 instead of 1.0.0-rc.4. I just submitted another PR to the components/ember repo (here) to resolve the issue.

[rwjblue]

@joefiorini - That's great! We could just use the normal Ember publishing process, and link directly to the 'stable' version in bower.json. Like so (we can't use ember-latest.js as you described above to future proof since that points to master):

{
  "name": "ember-app-kit",
  "dependencies": {
    "ember": "http://builds.emberjs.com/ember-1.0.0-rc.6.1.js",
    "handlebars": "1.0.0-rc.4",
    "jquery": "~1.9.1"
  }
}

The only (small) downside is that it then names the file vendor/ember/index.js, but that isn't a huge issue.

If we do this, we can just get rid of the reliance on the components/ember repo, and not add more work to the current publishing process.

I'll work up a PR for this change.

[stefanpenner]

we seem to be 6.1 now.

[rwjblue]

It was updated in #60, but this issue didn't get closed auto_magic_ally...

[joefiorini]

@rjackson So last week it looked like there was a bower.json on S3, but now it's gone. Do you have any idea what might have happened? Maybe @stefanpenner knows?

[rwjblue]

@joefiorini - I recently spoke with @wycats and he indicated that he would like to have better bower support, so maybe the team would be open to getting a bower.json generated as part of the publish process.

Background: I have been working on an update to ember-dev that will generate the various files (ember.js, ember.min.js, ember.prod.js) into subdirectories. See emberjs/ember-dev#24 for more details.

I think that we might be able to generate a bower.json into the specific sub-directory which would allow us to use builds.emberjs.com/latest/bower.json or builds.emberjs.com/stable/bower.js and then let bower deal with the updated versioning and whatnot.

I think that we need to have a bower.json template included in the repo (or generated by the build process), and just update the version tag for the specific commit. Once emberjs/ember-dev#24 is merged we can look at outputting the right values.