-
Notifications
You must be signed in to change notification settings - Fork 676
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
Make a release #269
Comments
I'd say the libc change bumps it up to 0.5.0 alone. There've been quite a few changes all around, it certainly warrants it. If there's a 0.7.0 a few weeks later then so be it. |
That makes sense. Now we need to figure out how to make a release... @carllerche, hi! |
This was referenced Feb 28, 2016
Closed
We have a 0.5.0! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The last release was over two months ago, and a lot of new APIs have been added, as well as bumping libc to 0.2.x. Not sure whether this should be a 0.4.3 or a 0.5.0 release. The changes that make me think it might be better as 0.5.0 are:
SigAction::new
changed: Account for the different signal handler types. #241A concern: we have #230 that has been dormant pending discussion in #221 (also dormant!). Depending on when and how that is resolved, it could be we'll have another backwards incompatible change fairly soon. I still think making a release sooner than later is worthwhile.
The text was updated successfully, but these errors were encountered: