b4n left a comment (geany/geany#4414) My current plan if nobody stops me before let's say tonight is: * Merge #4485 * Merge this (#4414) * Rebase and cleanup #4472 * Test the bundle in the native CI (basically like we do in the cross-build, that actually caught an issue even if we didn't want to see it)
So, @giuspen @eht16 @techee speak now or ~~forever hold your peace~~ open an issue or PR later :slightly_smiling_face: FWIW, the reason why I'd like to get on with this is threefold: * Current state is *not* release material (bundle not working on a fresh Windows 11, and probably nowhere) * I don't find a lot of spare time lately, and the Windows subject doesn't seem to thrill a lot of people and reviews seem fairly hard to come by (not a blame, I'm not very available nor super-thrilled either, but maybe for the fact I finally stumbled across a proper fix); so I kind of feel like it's easier on this matter to (carefully) act and see how it goes (especially with the above point) * There are several interdependent PRs so waiting makes things more frustrating (admittedly I could make one big "Windows stuff" aggregating them all, but it'd be slightly less clean, and see point 2 above) But as usual I'm happy to hold if anybody has objections (even if it's just like *wait! I want to test this **before** but won't have time before a week or two, so just hold your horses!*). I'm just saying that I won't follow the unwritten habit of waiting 2-or-so weeks of silence before merging one's own fix :slightly_smiling_face: -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/4414#issuecomment-3651336922 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/pull/4414/[email protected]>
