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

Winit version 0.28.0 #2634

Merged
merged 1 commit into from
Feb 2, 2023
Merged

Conversation

kchibisov
Copy link
Member

@kchibisov kchibisov commented Jan 17, 2023

Patches that left

Some of the patches that might be worth merging for 0.28.0:

If I've missed something or you want some bug to be fixed for v0.28.0 let me know.

Be aware that the next major release after the 0.28.0(0.29.0) will contain the new Wayland backend (updated to new wayland-rs) and likely new X11 backend(mixture of Xlib + Xcb, instead of raw xlib).

--
CC of some main downstream consumers(if you're not interested in getting notified about release planning in winit let me know, so I won't even CC you again).

If you have some issues with winit that you want fixed for 0.28.0 let me know while we're in release preparation stage, so I include them and try to look into.

Also would you prefer if winit had rc period or you're fine with the current policy with patch fixes right away, given that winit don't really have breaking changes. Initially
we decided to not do rc releases, since it's easier to iterate and propagate the update without them, given that majority unlikely to use them and it's better to know that something broke if you push the update.

@alice-i-cecile
Copy link

#2605 is the most important of those for us at Bevy :)

@Wumpf
Copy link
Contributor

Wumpf commented Jan 17, 2023

#2636 is blocking an egui PR for maximizing windows, would love to see that in if possible (:

@madsmtm madsmtm added the S - maintenance Repaying technical debt label Jan 21, 2023
@madsmtm madsmtm added this to the Version 0.28 milestone Jan 21, 2023
@MarijnS95
Copy link
Member

MarijnS95 commented Jan 30, 2023

@rib we have no breaking changes planned anymore for android-activity, right? Just making sure, otherwise we might want to push that out and update winit right before releasing 0.28.

(EDIT: And if not, we should do a nonbreaking patch release for the recent contributions, i.e. to reduce logcat spamming 🙂)

@madsmtm madsmtm mentioned this pull request Jan 30, 2023
Copy link
Member

@madsmtm madsmtm left a comment

Choose a reason for hiding this comment

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

I think we should go for the new release now, all the requested changes have been made (or I've written a description on them as to why we'll delay with it).

@madsmtm madsmtm marked this pull request as ready for review January 30, 2023 11:50
@kchibisov
Copy link
Member Author

The option as alt PR is still up, and I'll try to finish it today... The Alt PR should be trivial to finish anyway.

@rib
Copy link
Contributor

rib commented Jan 30, 2023

@rib we have no breaking changes planned anymore for android-activity, right? Just making sure, otherwise we might want to push that out and update winit right before releasing 0.28.

(EDIT: And if not, we should do a nonbreaking patch release for the recent contributions, i.e. to reduce logcat spamming 🙂)

Right, no breaking changes planned currently.

Doing a release for the logging cleanup should be fine. It'll also propagate the new url for the repo.

@rib
Copy link
Contributor

rib commented Jan 30, 2023

I had a few winit Android issues I started looking at and had wanted to make more progress with (ime + surface_size) but it's fine if those things slip to the next release.

For Android I've been looking more at issues in the JNI crate recently since I want to use it in the Android backend for Winit and but it has had a bunch of ergonomic and safety issues that I think need addressing first - so I've been a bit distracted from winit and android-activity.

@emilk
Copy link
Contributor

emilk commented Jan 30, 2023

I've tested latest winit with eframe and it seems to we working flawlessly, FWIW. I really like the new WindowEvent::TouchpadMagnify event ❤️

@kchibisov
Copy link
Member Author

I'll schedule release for today's evening (UTC+3). If no-one has anything else to add I'd push a release.

@dhardy
Copy link
Contributor

dhardy commented Jan 31, 2023

Winit master works with KAS; the one slight concern I note is that EventLoopWindowTargetExtWayland is now under cfg(wayland_platform) which is less easy to reproduce under downstream crates. For Winit 0.27 it's mostly copy-paste:

#[cfg(any(
    target_os = "linux",
    target_os = "dragonfly",
    target_os = "freebsd",
    target_os = "netbsd",
    target_os = "openbsd"
))]
{
    use winit::platform::unix::EventLoopWindowTargetExtUnix;
    if elwt.is_wayland() {
        // Wayland-specific code here
    }
}

Now one needs to read the build.rs, but at least that has a similar cfg there (due to "XXX aliases are not available for the build script itself").

No action needed; better docs may be possible.

@kchibisov
Copy link
Member Author

nah, will wait for #2665...

@kchibisov kchibisov merged commit 86bbb1c into rust-windowing:v0.28.x Feb 2, 2023
@MarijnS95
Copy link
Member

@kchibisov thanks for releasing! Can you now clean up some of the branch inconsistencies? There's a 0.27 branch that points to the 0.27.1 release whereas 0.27.x points to the latest 0.27.5 release. And the new v0.28.x branch has a v in front of it; replicate that on the other branch?

@madsmtm somehow strangely we seem to have some feature resolver problems on Rust 1.59 getting to objc2 = "=0.3.0-beta.3": https://github.com/ash-rs/ash/actions/runs/4072998223/jobs/7016396013, any idea/suggestions?

@kchibisov
Copy link
Member Author

@MarijnS95 msrv is 1.60 not 1.59 for the new winit.

@kchibisov
Copy link
Member Author

@kchibisov thanks for releasing! Can you now clean up some of the branch inconsistencies? There's a 0.27 branch that points to the 0.27.1 release whereas 0.27.x points to the latest 0.27.5 release. And the new v0.28.x branch has a v in front of it; replicate that on the other branch?

I'll try to look into that, but not sure if I can change much.

@MarijnS95
Copy link
Member

MarijnS95 commented Feb 2, 2023

@kchibisov right, silly of me to expect cargo to complain about Rust 1.59 being too low for the set MSRV of 1.60 in winit before trying (and failing) to resolve winit's dependencies...

@madsmtm

This comment was marked as duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S - maintenance Repaying technical debt
Development

Successfully merging this pull request may close these issues.

8 participants