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

v0.30.0 release planning #3476

Closed
madsmtm opened this issue Feb 9, 2024 · 11 comments
Closed

v0.30.0 release planning #3476

madsmtm opened this issue Feb 9, 2024 · 11 comments
Labels
S - meta Project governance

Comments

@madsmtm
Copy link
Member

madsmtm commented Feb 9, 2024

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.

@madsmtm madsmtm added the S - meta Project governance label Feb 9, 2024
@madsmtm madsmtm added this to the Version 0.30.0 milestone Feb 9, 2024
@madsmtm madsmtm pinned this issue Feb 9, 2024
@madsmtm madsmtm added the C - nominated Nominated for discussion in the next meeting label Mar 28, 2024
@madsmtm
Copy link
Member Author

madsmtm commented Mar 28, 2024

I'd like to move forwards with the v0.30 release soon, looking at the milestone I'm unsure of what blockers there are except for #3477?

@madsmtm
Copy link
Member Author

madsmtm commented Mar 29, 2024

Might also want to block on #3590, it's somewhat related to the migration entries.

@daxpedda
Copy link
Member

daxpedda commented Apr 1, 2024

I would only block on #3477.

@daxpedda
Copy link
Member

Lets not forget #2325.

@kchibisov
Copy link
Member

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.

@torokati44
Copy link
Contributor

Is there going to be a 0.30 alpha/beta/RC release before final, so users can more easily (and sooner) experiment with the migration?

@madsmtm
Copy link
Member Author

madsmtm commented Apr 22, 2024

I don't think we were planning to do so

@torokati44
Copy link
Contributor

I see, thank you!

@kchibisov
Copy link
Member

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.

@madsmtm
Copy link
Member Author

madsmtm commented Apr 26, 2024

We decided today to wait for the ndk update to 0.9, at the very latest release Winit 0.30 at next week's meeting

@kchibisov
Copy link
Member

Release done.

@madsmtm madsmtm removed the C - nominated Nominated for discussion in the next meeting label May 3, 2024
@madsmtm madsmtm unpinned this issue May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S - meta Project governance
Development

No branches or pull requests

4 participants