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

[BUGFIX beta] Bump Ember & Ember Data version to 2.6.0-beta #5859

Merged
merged 2 commits into from
Apr 28, 2016

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented Apr 28, 2016

No description provided.

@Turbo87
Copy link
Member

Turbo87 commented Apr 28, 2016

I thought we decided to stay on the stable versions?

@rwjblue
Copy link
Member Author

rwjblue commented Apr 28, 2016

I discussed with @stefanpenner a few days ago about it. It is possible that I misunderstood, but since ember-cli@2.6.0 will install ember@2.6.0 it seems reasonable that using the betas of ember-cli@2.6 would also use the beta versions of Ember.

@Turbo87
Copy link
Member

Turbo87 commented Apr 28, 2016

does that mean that our canary should also use ember canary?

@rwjblue
Copy link
Member Author

rwjblue commented Apr 28, 2016

In theory yes, but Ember canary is a bit too unstable at the moment (due to all the work being done on glimmer2) so I think we should stick to tagged releases.

@Turbo87
Copy link
Member

Turbo87 commented Apr 28, 2016

shouldn't this PR target ember-cli:beta?

@rwjblue
Copy link
Member Author

rwjblue commented Apr 28, 2016

@Turbo87 - All changes to beta go through master first, and are then cherry-picked into beta. Otherwise it is very easy for the two to get out of sync.

@rwjblue rwjblue changed the title [BUGFIX beta] Bump Ember version to 2.6.0-beta.2. [BUGFIX beta] Bump Ember & Ember Data version to 2.6.0-beta Apr 28, 2016
@Turbo87
Copy link
Member

Turbo87 commented Apr 28, 2016

hmm okay... the way I've usually worked in most other projects is regularly merging release/stable/beta back into master to prevent them from falling out of sync. any advantages/disadvantages I should be aware of?

@rwjblue
Copy link
Member Author

rwjblue commented Apr 28, 2016

@Turbo87 - Due to our train model where all changes flow from canary down into the final release, we need to ensure that changes also follow the same pattern. In this case, I made a mistake when doing the initial 2.6.0-beta.1 release as these changes should have been included there to begin with (and no cherry-picking or merging would have been needed). In most other cases, we want the fixes to land on canary so they can be tested by those brave souls running canary before rolling things into beta or release branches.

@rwjblue
Copy link
Member Author

rwjblue commented Apr 28, 2016

I'm happy to discuss a different pattern for doing these sorts of things going forward, but I'd like to land this for now....

@rwjblue
Copy link
Member Author

rwjblue commented Apr 28, 2016

@homu r+

@homu
Copy link
Contributor

homu commented Apr 28, 2016

📌 Commit bdb45d1 has been approved by rwjblue

@homu
Copy link
Contributor

homu commented Apr 28, 2016

⚡ Test exempted - status

@homu homu merged commit bdb45d1 into ember-cli:master Apr 28, 2016
homu added a commit that referenced this pull request Apr 28, 2016
[BUGFIX beta] Bump Ember & Ember Data version to 2.6.0-beta

None
@rwjblue rwjblue deleted the bump-ember-version branch April 28, 2016 16:00
@Turbo87
Copy link
Member

Turbo87 commented Apr 28, 2016

I'm happy to discuss a different pattern for doing these sorts of things going forward, but I'd like to land this for now....

sure, I didn't intend to block this. was just curious :)

@Turbo87 Turbo87 added this to the v2.6.0 milestone May 9, 2016
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

Successfully merging this pull request may close these issues.

None yet

3 participants