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

WIP: Tag 0.6.0-pre.beta #21232

Merged
merged 1 commit into from
Mar 31, 2017
Merged

WIP: Tag 0.6.0-pre.beta #21232

merged 1 commit into from
Mar 31, 2017

Conversation

tkelman
Copy link
Contributor

@tkelman tkelman commented Mar 30, 2017

To be sure we don't accidentally tag a beta where anything's regressed relative to alpha, I want to run pkgeval here. If anyone has anything they must get merged, please do so then leave master alone long enough for it to run. Takes about 8-10 hours for the whole thing, and since I'm paranoid, any possibly-breaking change warrants running it again just to be sure.

(this should also be squash-merged when it's ready, to avoid confusing the version count)

@tkelman tkelman merged commit bd84fa1 into master Mar 31, 2017
@tkelman tkelman deleted the tk/beta branch March 31, 2017 12:59
@tkelman
Copy link
Contributor Author

tkelman commented Mar 31, 2017

pkgeval looked fine https://gist.github.com/fcfa5db80795959e0828c1fb15c8acad

it's supposed to run the same set of packages with both, not sure exactly why that didn't happen here. maybe vagrant being flaky.

@timholy
Copy link
Member

timholy commented Apr 2, 2017

Just noticed we got bumped to beta. I'm sure it depends entirely on the kinds of workloads one runs, but to me we still feel like "alpha." #21141/#21006/#20703 and #21250/#21243 are serious bugs. (I still can't use 0.6 for real work.)

@iamnapo iamnapo mentioned this pull request Apr 5, 2017
@timholy
Copy link
Member

timholy commented Apr 21, 2017

I'd like to commend the folks who did so much over the last few weeks (and earlier, of course) to solidify 0.6. I'm starting to switch to it as my default; that will take some time to complete, because I have a lot of code to convert over. But I've been noticing that just about any time I find a weakness of 0.5, it seems that 0.6 has already addressed it.

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.

2 participants