Wine Staging 11.19 lands as a rebase, not a feature drop
The patch-based Wine fork goes live on October 3, built on Wine's freshest development code. Nothing new ships, and that's largely the point.
Wine Staging 11.19 is out. It landed today and tagged by maintainer Alistair Leslie-Hughes, and it rides the newest version of the core Wine development branch. If you were hoping for a fresh batch of experimental patches, you're out of luck. The staging patch set is identical to v11.18. No stages added. No stages removed.
Instead this is a maintenance pass. Wine Staging rebases its hundreds of patches onto the latest upstream Wine roughly every two weeks, and 11.19 is just the latest turn of that wheel. It keeps the experimental bundle current without changing what's inside the box.
Wine has been chugging along since 1993. After more than three decades it's still not an emulator or a virtual machine, so the distinction still matters: it re-implements the Windows API in user space rather than spinning up a separate Windows instance. Staging is the aggressive cousin of that core project, full of patches that WineHQ hasn't quite decided are ready for the main branch.
What actually changed
The work behind 11.19 was mostly plumbing. Between the v11.18 tag on September 18 and the v11.19 tag on October 3, the staging branch was rebased three times onto progressively newer Wine development commits. Each set of patches got re-applied on top of newer core Wine code, conflicts resolved along the way. That keeps staging roughly in lockstep with the Wine 11.x development line.
A few stages did get refreshed in place. The vkd3d-latest patch-set was updated several times across the cycle, and it's the one most relevant to gamers since it's the Direct3D 12-to-Vulkan translation layer. The odbc32-fixes stage also moved, tracking a fix tied to Wine bug report #7955.
Overall the commit history between the two tags is tight. Just 11 commits, all by Leslie-Hughes. Most are rebase commits. The rest refresh specific stages. This is entirely standard for Wine Staging, which rebases rather than developing on a divergent branch, so a given release rarely carries many commits. The real feature work happens in the individual patch-sets, authored by a wider community, then folded in at the next rebase.
What 11.19 actually ships
No new stages, but the set still numbers 119 patch-sets. That's a lot of niche, application-specific fixes spanning graphics, audio, input, networking, and core Windows libraries. A few show the kind of work staging is built around.
The d3drm-starwars stage stops crashes in older titles like Star Wars Rebellion and Lego Islands by stubbing parts of a legacy Direct3D Rendering Module API. The wined3d_unorm_srgb stage adds sRGB color handling, which rescues the almost-unplayable darkness in Frostpunk. There's an HTTP implementation for Media Foundation that helps games like The Good Life, plus a GIF encoder for the first time.
It's a kitchen-sink approach. Some of it is solid. Some of it is still experimental, and that's the whole trade-off: staging runs more Windows applications out of the box than stock Wine, but it's less conservative and occasionally less stable. You can even build selectively, enabling only the stages you care about.
How this differs from standalone Wine 11.19
Keep in mind that there's also a standalone Wine 11.19, announced a day earlier on October 2. It carries the headlines: vertical text support in GDIPlus, DNS query caching, an update to Unicode tables (18.0.0), and VBScript parser improvements. That work is aimed at eventually landing in a future stable Wine release.
Wine Staging 11.19 adds none of that on its own. It just packages the current development code alongside staging's experimental patches. So a staging user gets both the newest Wine base and the extra compatibility fixes, just on a more experimental path than standalone Wine 11.19 would offer.
How to get it
The source tree for v11.19 sits at the wine-staging repository tag v11.19. Building it means running a Wine development build environment, then executing staging/patchinstall.py to apply all the stages in order before compiling.
If you'd rather not build from scratch, pre-built packages for a range of Linux distributions and macOS are up on the official WineHQ download pages. Head here to the WineHQ wiki's Download page for the links. On most distros, the wine-staging package installs to /opt/wine-staging, so the binaries show up as /opt/wine-staging/bin/wine and /opt/wine-staging/bin/winecfg.
The project is run by volunteers, and it takes donations through Patreon to fund testing across hardware, games, and applications. Patches traditionally come through WineHQ bug reports rather than GitHub pull requests, so if you want to contribute, that's where the door is.
