-
Notifications
You must be signed in to change notification settings - Fork 231
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
Add links to OS documentation, attempt 3 #319
Conversation
43b506d
to
d6a1c42
Compare
I notice that you have an open tracking issue for a breaking release. Is the MSRV bump happening as part of a breaking release? |
Socket2 bumping MSRV as an 0.x.0 release would be fine for us downstream (Tokio), but Tokio needs at a minimum 1.49.0 for socket2 0.4.x |
It's a year old so I figure it's ok, but we can bump to 0.5.x.
I though Tokio supported 6 months of Rust versions. Is this for a LTS release? |
@Thomasdezeeuw yes, but we also don't break MSRV in patch releases. If |
I'll start the v0.5.x version and update rustc to 1.62 (has creation of |
Created #320 for v0.5, I've updated the MSRV to 1.62, aiming to support 1.63 (for I/O safety). |
40e37d2
to
461a4cb
Compare
Replaces #248.
This increases MSRV to 1.54 (released nearly a year ago).