December 2025 - Wine-Devel - list.winehq.org

Wine staging 11.0-rc1 release

by Alistair Leslie-Hughes

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 11.0-rc1 (253 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * None Removed (No longer required). * None Added: * None Updated: * vkd3d-latest Where can you help * Run Steam/Battle.net/GOG/UPlay/Epic * Test your favorite game. * Test your favorite applications. * Improve staging patches and get them accepted upstream. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

Dec. 6, 2025

Welcome to code freeze!

by Alexandre Julliard

Folks, With the release of 11.0-rc1, we are now officially in the code freeze period. Many thanks to everybody for another year of great work! During code freeze, only small, targeted bug fixes will be accepted. When sending fixes, please make sure to mention the bug or the app that is fixed by the change. We are starting code freeze with 200 pending regressions, which is significantly lower than in previous years, where the number was more around 230. It remains to be seen how many regression bugs will be filed against rc1, but I'm hopeful that we can release 11.0 with fewer pending regressions that the previous stable releases. As usual, there will now be weekly -rc releases until the final 11.0, which is expected some time around mid-January. Thank you all for your work! -- Alexandre Julliard julliard(a)winehq.org

Dec. 5, 2025

Re: Core Infrastructure Maintenance 2025-12-10 18:00 UTC

by David Kahurani

MITm On Wed, Dec 3, 2025 at 1:19 AM DigitalOcean Support <support(a)digitalocean.com> wrote: > > Start: 2025-12-10 18:00 UTC > End: 2025-12-10 20:00 UTC > > Hello, > > During the above window, our Engineering team will be performing maintenance on principal infrastructure in order to improve reliability of the services. Please note that existing infrastructure will continue running without issue. This maintenance impacts create, read, update, and delete (CRUD) operations in all regions. > > Expected Impact: > > During the maintenance window, users may experience increased latency for the following platform operations: > > Cloud Control Panel and API operations > Event processing > Droplet creates, resizes, rebuilds, and power events > Managed Kubernetes reconciliation and scaling > Load Balancer operations > Container Registry operations > App Platform operations > Managed Database creation and scaling > > We expect to see two periods of 10 second impact, for a total of 20 seconds within the hour window. If unexpected impact occurs or continues for longer than expected, we will provide updates via our public status page. > > If you have any questions related to this issue please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket > > Thank you, > Team DigitalOcean

Dec. 2, 2025

Re: Introducing the list.winehq.org domain

by David Kahurani

My birthday is on the 6th of December I already turned down yet another...holiday I do wish, however to attend the one on 12th December On Tue, 2 Dec 2025, 22:15 Alexandre Julliard, <julliard(a)winehq.org> wrote: > Folks, > > We are now ready for the second phase of the Wine mailing lists > migration, where we will move the lists to a different server. We have > selected mailmanlists.net to host our lists. > > The plan is for the migration to happen on Monday December 8. There may > be a downtime of a few hours while we get everything settled. > > This will result in the following changes: > > - It will be necessary to use the @list.winehq.org domain to post to the > lists, so for instance <wine-devel(a)list.winehq.org>. The old > @winehq.org addresses will no longer work. We considered setting up > forwarding, but apparently this doesn't work well, and was strongly > discouraged by the MailmanLists people. > > - The List-Id: header will change, so you'll need to update your > filters. > > - The subscribers lists will be transferred, so your subscriptions will > be preserved. > > - The mailing lists archives will be transferred, and will be available > at the same address (https://list.winehq.org/mailman3/hyperkitty/) > > - User accounts will *not* be transferred, so if you had created an > account on the old server you'll need to re-create one on the new > server (an account is not necessary to subscribe to the lists, but it > can be useful if you want to change your preferences) > > Please let me know if you have any questions or concerns, > > -- > Alexandre Julliard > julliard(a)winehq.org > > >

Dec. 2, 2025

Re: Introducing the list.winehq.org domain

by Alexandre Julliard

Folks, We are now ready for the second phase of the Wine mailing lists migration, where we will move the lists to a different server. We have selected mailmanlists.net to host our lists. The plan is for the migration to happen on Monday December 8. There may be a downtime of a few hours while we get everything settled. This will result in the following changes: - It will be necessary to use the @list.winehq.org domain to post to the lists, so for instance <wine-devel(a)list.winehq.org>. The old @winehq.org addresses will no longer work. We considered setting up forwarding, but apparently this doesn't work well, and was strongly discouraged by the MailmanLists people. - The List-Id: header will change, so you'll need to update your filters. - The subscribers lists will be transferred, so your subscriptions will be preserved. - The mailing lists archives will be transferred, and will be available at the same address (https://list.winehq.org/mailman3/hyperkitty/) - User accounts will *not* be transferred, so if you had created an account on the old server you'll need to re-create one on the new server (an account is not necessary to subscribe to the lists, but it can be useful if you want to change your preferences) Please let me know if you have any questions or concerns, -- Alexandre Julliard julliard(a)winehq.org

Dec. 2, 2025