Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we do versioning lockstep? #64

Closed
hhff opened this issue Jul 31, 2015 · 3 comments
Closed

Should we do versioning lockstep? #64

hhff opened this issue Jul 31, 2015 · 3 comments

Comments

@hhff
Copy link
Collaborator

hhff commented Jul 31, 2015

Summoning @kellyselden @mike-north

Wondering if it makes more sense to lock the version here to Ember CLI? That way we just guarantee that it supports the corresponding Ember CLI version (and it's bundled Ember & Ember Data versions)...

I see pros & cons to it.

Thoughts team? @stefanpenner / @rwjblue do you think minor addons should adopt the lock-step versioning approach also?

@rwjblue
Copy link
Member

rwjblue commented Jul 31, 2015

I personally think that addons should use useful version numbers for their consumers (aka not lockstep).

@mike-north
Copy link
Collaborator

agree with @rwjblue. Ideally there isn't tight coupling between addons and framework minor/patch versions. Ember-data is an exception

@hhff
Copy link
Collaborator Author

hhff commented Jul 31, 2015

word!

@hhff hhff closed this as completed Jul 31, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants