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.

Sign up for GitHub

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

Jump to bottom

Release plan for support on tokio v0.3? #130

Closed
fanatid opened this issue Nov 30, 2020 · 6 comments · Fixed by #141
Closed

Release plan for support on tokio v0.3? #130

fanatid opened this issue Nov 30, 2020 · 6 comments · Fixed by #141

Comments

@fanatid
Copy link
Contributor

fanatid commented Nov 30, 2020

https://tokio.rs/blog/2020-10-tokio-0-3
@fanatid fanatid mentioned this issue Nov 30, 2020
Closed
28 tasks
@fussybeaver
Copy link
Owner

Currently blocked in bollard by tokio-rs/tokio#3118

@chrisabruce
Copy link

I would appreciate v0.3 as well.

@jmjoy
Copy link

jmjoy commented Jan 7, 2021

Should upgrade to tokio v1 now.

@fussybeaver
Copy link
Owner

Pending tokio-rs/tokio#3388

@lukesteensen lukesteensen mentioned this issue Jan 20, 2021
Merged
10 tasks
@lynzrand lynzrand mentioned this issue Feb 16, 2021
Merged
@dfreese
Copy link

dfreese commented Feb 25, 2021

It kind of looks like the design discussion in tokio-rs/tokio#3511 looks like it has stalled.

Given #140, would it be possible to release 0.10?

I haven't gotten too far in my search yet, but perhaps https://github.com/LucioFranco/tokio-compat-02 might help pull back in named pipe support in the meantime.

@fussybeaver
Copy link
Owner

Yep, I want to publish a new bollard-stubs version, since the upstream API got bumped to 1.41 and should be good to go.

@fussybeaver fussybeaver mentioned this issue Feb 27, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Release 0.10 fussybeaver/bollard
5 participants
@chrisabruce @fanatid @dfreese @jmjoy @fussybeaver