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

Add blogpost of Mio 0.7 alpha 1 announcement #345

Merged
merged 8 commits into from
Dec 17, 2019
Merged

Add blogpost of Mio 0.7 alpha 1 announcement #345

merged 8 commits into from
Dec 17, 2019

Conversation

Thomasdezeeuw
Copy link
Contributor

This announces Mio 0.7 alpha 1.

There are a number of TODOs left which I'll clean up during the course of the week, I just wanted some feedback. My personal writing style is a bit impersonal and we might want to change that.

/cc some major contributors to the release @carllerche, @PerfectLaugh, @kleimkuhler, @asomers, @FXTi.

P.S. English isn't my first language and I'm (very) dyslexic so there will be grammar/language mistakes :)

@Thomasdezeeuw
Copy link
Contributor Author

@sfackler mentioned on chat that Linux < 4 is a little broad. I need to figure out what minimal Linux version we actually support.

Also see tokio-rs/mio#1072 and tokio-rs/mio#853.

Copy link

@asomers asomers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for writing this blog post. It will be very helpful to mio's users. But there's one big question that it doesn't address. How can a mio 0.6-based crate that implements Evented move to mio 0.7? That's the situation that mio-aio is in.

content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
Copy link
Member

@hawkw hawkw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some spelling and grammar edits. I hope they're useful!

content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
@Thomasdezeeuw
Copy link
Contributor Author

Thnak you @asomers and @hawkw for the thorough review. I've fixes all problems you've indicated, please let me know if I missed any or if you found more.

content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
content/blog/2019-11-mio-v0.7-alpha.md Outdated Show resolved Hide resolved
@Thomasdezeeuw
Copy link
Contributor Author

@asomers fixes the last two things.

@Thomasdezeeuw
Copy link
Contributor Author

Thanks for writing this blog post. It will be very helpful to mio's users. But there's one big question that it doesn't address. How can a mio 0.6-based crate that implements Evented move to mio 0.7? That's the situation that mio-aio is in.

This something that the blog post is indeed missing. For mio-aio I think you can register the fd directly using SourceFd.

@Thomasdezeeuw Thomasdezeeuw marked this pull request as ready for review December 13, 2019 23:00
Copy link

@kleimkuhler kleimkuhler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly typo comments

content/blog/2019-12-mio-v0.7-alpha.1.md Outdated Show resolved Hide resolved
content/blog/2019-12-mio-v0.7-alpha.1.md Outdated Show resolved Hide resolved
content/blog/2019-12-mio-v0.7-alpha.1.md Outdated Show resolved Hide resolved
content/blog/2019-12-mio-v0.7-alpha.1.md Outdated Show resolved Hide resolved
content/blog/2019-12-mio-v0.7-alpha.1.md Outdated Show resolved Hide resolved
@Thomasdezeeuw
Copy link
Contributor Author

Thanks @kleimkuhler I've fixed all bugs.

@Thomasdezeeuw
Copy link
Contributor Author

I meant type-o's, it's getting late here.

Copy link

@kleimkuhler kleimkuhler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Copy link

@dtacalau dtacalau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@carllerche
Copy link
Member

@Thomasdezeeuw what about adding a blurb like this at the top:

We are excited to announce [Thomas de Zeeuw][Thomasdezeeuw] as
the new lead of Mio. Mio is the low level I/O portability abstraction that
backs Tokio and other Rust projects. Thomas has been behind most of
the Mio 0.7 effort and will be continuing to lead the crate to 1.0. He has
written the rest of the announcement.

[Thomasdezeeuw]: github.com/Thomasdezeeuw

@Thomasdezeeuw Thomasdezeeuw merged commit 280c874 into tokio-rs:master Dec 17, 2019
@Thomasdezeeuw Thomasdezeeuw deleted the mio-v0.7 branch December 17, 2019 15:36
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 this pull request may close these issues.

6 participants