-
Notifications
You must be signed in to change notification settings - Fork 921
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
v0.30.0
release planning
#3476
Comments
I'd like to move forwards with the |
Might also want to block on #3590, it's somewhat related to the migration entries. |
I would only block on #3477. |
Lets not forget #2325. |
I know, I'll update it right at the end. Though, we can discuss the options I have set on it. |
Is there going to be a |
I don't think we were planning to do so |
I see, thank you! |
Old APIs are deprecated and not yet removed, so you don't have rc, etc, because they are still there, you'll just get a warning for them. Some were changed, but preserving semantics, so it's not really a breaking change either. |
We decided today to wait for the |
Release done. |
Winit is moving towards a trait-based API, users can submit feedback on their migration here.
To this end, we will use Winit
v0.30
as a migration step, where both the trait-based and the current closure-based APIs will be available, such that we can solicit feedback from users, and hopefully make the transition less painful.Check out the milestone for the current schedule.
The text was updated successfully, but these errors were encountered: