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

Any plans for 0.8.0? #519

Closed
steveklabnik opened this issue Feb 22, 2017 · 14 comments · Fixed by #546
Closed

Any plans for 0.8.0? #519

steveklabnik opened this issue Feb 22, 2017 · 14 comments · Fixed by #546

Comments

@steveklabnik
Copy link
Contributor

It's been five months and almost 200 commits since 0.7.0, just curious if/when 0.8.0 would get cut. Thanks!

@posborne
Copy link
Member

Yeah, it is overdue. I think we just go ahead and cut one now. Thought @kamalmarhubi @fiveop @nix-rust/nix-maintainers ?

@kamalmarhubi
Copy link
Member

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 :/

@kamalmarhubi
Copy link
Member

@posborne let's wrap up a few outstanding PRs that are really close, then release? And no later than Friday...

@kamalmarhubi
Copy link
Member

kamalmarhubi commented Feb 24, 2017

Ok, I propose we let the following PRs get merged then cut 0.8:

@kamalmarhubi
Copy link
Member

Those libc PRs are merged. Asked for a release in rust-lang/libc#539

@fiveop
Copy link
Contributor

fiveop commented Feb 25, 2017

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 :)

@asomers
Copy link
Member

asomers commented Feb 26, 2017

Can we please wait for the release until after PR #506 finishes? That PR changes an API that was introduced after 0.7.0.

@kamalmarhubi
Copy link
Member

Quick status update: libc release is blocked on rust-lang/libc#538 (unrelated but soon-to-be-merged).

@kamalmarhubi
Copy link
Member

kamalmarhubi commented Feb 28, 2017

Selfishly going to add #540 and #541 to the blocking list. 👿

@Susurrus
Copy link
Contributor

I'd also like to nominate #527 which is done and just waiting on CI to finish.

@kamalmarhubi
Copy link
Member

kamalmarhubi commented Mar 1, 2017

@Susurrus I think you'll get your chance: yesterday's S3 outage delayed rust-lang/libc#538... :-)

@kamalmarhubi
Copy link
Member

@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!

kamalmarhubi added a commit to kamalmarhubi/nix-rust that referenced this issue Mar 2, 2017
@Susurrus
Copy link
Contributor

Susurrus commented Mar 2, 2017

@kamalmarhubi Ack.

@homu homu closed this as completed in #546 Mar 2, 2017
homu added a commit that referenced this issue Mar 2, 2017
@kamalmarhubi
Copy link
Member

This is now tagged and published. Need to figure out how to get the changelog in the github release page some time.

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 a pull request may close this issue.

6 participants