-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Prepare 0.4 release with tokio 1.0 #443
Comments
I was looking around to find an indicator when tokio 0.3 will be released (roughly). Do you have any reference to for that? |
@saschagrunert soon, we are currently working on it, there should be a milestone in the tokio repo for it. |
Tokio 0.3 has been released! |
Work will be going into hyper to get that upgrade so it will be a few days at a min before a new version of tonic, but we are working hard to get there! |
See hyperium/hyper#2302 for further information |
@LucioFranco |
Is the intention still to support tokio 0.3, or to jump straight to the 1.0 release? |
Imho it would be better if we switched directly to tokio 1.0 |
Hey all sorry for the delay, the plan is this:
This is what is planned, but its not trivial atm. That said, my focus the last few months (even longer tbh) has been on tokio since we have needed a solid foundation there. Now that my work there is mostly complete (it was to help get it to 1.0), I can now focus on other areas of the stack. Writing this as of the 28th of Dec and I am on vacation till the new year, so won't get started on this until then. Hopefully, this gives some context on why things have been a bit slow here but now that tokio 1.0 is out there is a lot of planned work that I will finally get too in 2021. |
@LucioFranco thank you! |
Okay so a little update here, most deps have been updated. I have a PR open to fix the blocking bug. I don't currently have much time to fix all the transport issues so I will release My goal is to get |
tonic 0.4 has been released! enjoy! |
No description provided.
The text was updated successfully, but these errors were encountered: