The development release Wine 10.19 is out now for the compatibility layer that powers Valve’s Proton, here’s all that’s new and improved. Early next year we should see Wine 11, and then at some point Proton 11 too!
From the highlights:
Support for reparse points.
- More support for WinRT exceptions.
- Refactoring of Common Controls after the v5/v6 split.
- Typed Arrays support in JScript.
- Various bug fixes.
I wouldn’t want to keep the 11 in there. The entire reason for (hypothetically) making this change is to get away from the old version number and any potential confusion it might cause.
I also prefer smaller version numbers, so “subtract 2000 from year” works better for me (and there’s no better time to take advantage of the fact this produces sensible numbers), but I can see why the full year might be preferable for someone else.
How do you differentiate between significant major releases from a minor patch that just happens to release in Jan 1st? Use old year versioning?
Yeah. I think I have a preference for a three tier system that’s Y.R.P (e.g. 25.0.2; “Year”, Release within year, Patch number), so yes, I could imagine the third level being incremented the following year in an emergency.
And if two-tier is paramount, tricks like (R+1)*100+P will work provided there aren’t going to be 100 patches per release. (e.g. 25.102)