-
Notifications
You must be signed in to change notification settings - Fork 654
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
Any plans for 0.8.0? #519
Comments
Yeah, it is overdue. I think we just go ahead and cut one now. Thought @kamalmarhubi @fiveop @nix-rust/nix-maintainers ? |
I'm tempted to ask for a libc release, and then there's a tiny improvement we can get to one recently merged PR that I can't find right now :/ |
@posborne let's wrap up a few outstanding PRs that are really close, then release? And no later than Friday... |
Ok, I propose we let the following PRs get merged then cut 0.8:
|
Those libc PRs are merged. Asked for a release in rust-lang/libc#539 |
In the future, anyone of us should feel free to bump the version whenever a few changes have accumulated. Given how we seem to work on this project in spurts, this will not happen more often than once a month anyway :) |
Can we please wait for the release until after PR #506 finishes? That PR changes an API that was introduced after 0.7.0. |
Quick status update: libc release is blocked on rust-lang/libc#538 (unrelated but soon-to-be-merged). |
I'd also like to nominate #527 which is done and just waiting on CI to finish. |
@Susurrus I think you'll get your chance: yesterday's S3 outage delayed rust-lang/libc#538... :-) |
@Susurrus I'm going to push a PR to bump to v0.8.0 now. We'll get your changes in soon. There's no reason we went five months between releases; it's certainly not a policy! |
closes nix-rust#519
@kamalmarhubi Ack. |
It's been five months and almost 200 commits since 0.7.0, just curious if/when 0.8.0 would get cut. Thanks!
The text was updated successfully, but these errors were encountered: