6 ms·

Why not 1.10?

by jhasse 10y ago

Why not 1.10?

shakna 10y ago
> It marks the beginning of the code freeze period. Some parts of the code are getting frozen: [0] > This means that from now on, new features or code redesigns won't be accepted; only targeted bug fixes that don't look too dangerous will be allowed in. The freeze will get increasingly more strict... [0] https://www.winehq.org/pipermail/wine-devel/2015-November/110369.html https://www.winehq.org/pipermail/wine-devel/2015-November/11... Edit: My bad. See below.
- gravypod 10y ago
  Wine, the last time I used it, was no where near done. Is this the mark of major compatability with certian portions of the system that they've finally hammered out?
  - reitanqild 10y ago
    It could just be about breaking backwards compatibility although from a quick glance it seems more like they are signalling major milestone.
  - davidgerard 10y ago
    When was that, and for what? 'Cos in my experience - including using it to run commercial Windows software on a Linux box rather than use yet another standalone Windows box - it's surprisingly good and works more often than not. (The commercial use we were putting it to: part of a compiler chain for the red button functionality on satellite TV. Remember: if you're selling crufty proprietary vertical market software for $10k/seat/year, always put "Open" in the name.) I realise this is anecdote wars, but nevertheless it'd be interesting to know where it falls down.
    - cookiecaper 10y ago
      WINE works very well for most software that primarily utilizes common and mature APIs, which covers a lot of really great software, especially small, specialized utilities for niches that don't get a ton of commercial attention. It's generally the more complex and cutting-edge stuff that makes use of newer pieces of .NET, DirectX, or rarely-used components of obscure APIs that WINE struggles with. Unfortunately, a large amount of the interesting Windows-only software incorporates some of that stuff in one way or another. That's especially the case with games, which usually require very specific hand-optimization that invokes a lot of tricks. Then, to improve performance on AAA releases, driver vendors release updates that stack hacks-on-hacks. That makes gaming pretty tricky to successfully execute at performance-parity in WINE. I don't mean any of this critically, just addressing the issue. It's absolutely amazing what Alexandre et al have done so far. WINE is one of the most impressive software projects in the world, IMO. I was lucky enough to be able to contribute to it in a small way myself (patches to a prior generation of the audio engine). For many years I refused to play any game that didn't run well in WINE. Just this May, after 10 years on Linux desktop full-time, I switched back to a Windows desktop to get native performance out of my photography pipeline -- VMs just weren't cutting it, and WINE was a long way off from good support. Definitely a sad thing for me on a personal level.
      - davidgerard 10y ago
        > It's generally the more complex and cutting-edge stuff that makes use of newer pieces of .NET, DirectX, or rarely-used components of obscure APIs that WINE struggles with. Yeah, this is why Wine tends to use the "get the application to work" method. Thankfully a lotta the guys at Codeweavers are gamers who want their stuff to work too ;-) .NET is a friggin' nightmare IME, even after you've installed over half a gigabyte of Microsoft downloads.
        brianwawok 10y ago
        Net should get better over time with native Linux support no?
        JetSpiegel 10y ago
- jhasse 10y ago
  Hm ... Wine 1.8 also had a code freeze: http://www.phoronix.com/scan.php?page=news_item&px=Wine-1.8-Code-Freeze http://www.phoronix.com/scan.php?page=news_item&px=Wine-1.8-...
  - makomk 10y ago
    Every even-numbered Wine release is a stable release preceded by a code freeze. If they followed the normal pattern, this release would be Wine 1.10.
- saurik 10y ago
  From the wording, which I only point out as it seems like people reading your comment are being confused and maybe that means you are also confused, this is a standard code freeze for this one release: the idea being that on your way to a release, such as 2.0 (or 1.8), at some point you have to say "look, we are doing a release here, stop making major changes so we can fix some bugs and cut a version", and this "release candidate" "marks the beginning of the code freeze period" (implicitly for the release of 2.0).
- deleted 10y ago
  [deleted]
sp332 10y ago
According to the description of the WineConf keynote on this page, https://www.winehq.org/wwn/403 https://www.winehq.org/wwn/403 they're just switching to time-based releases. The mobile version of that page was broken for me, but switching to the desktop version helped.

Why not 1.10?

by jhasse 10y ago

Why not 1.10?

> It marks the beginning of the code freeze period. Some parts of the code are getting frozen: [0] > This means that from now on, new features or code redesigns won't be accepted; only targeted bug fixes that don't look too dangerous will be allowed in. The freeze will get increasingly more strict... [0] https://www.winehq.org/pipermail/wine-devel/2015-November/110369.html https://www.winehq.org/pipermail/wine-devel/2015-November/11... Edit: My bad. See below.

gravypod 10y ago
Wine, the last time I used it, was no where near done. Is this the mark of major compatability with certian portions of the system that they've finally hammered out?
- reitanqild 10y ago
  It could just be about breaking backwards compatibility although from a quick glance it seems more like they are signalling major milestone.
- davidgerard 10y ago
  When was that, and for what? 'Cos in my experience - including using it to run commercial Windows software on a Linux box rather than use yet another standalone Windows box - it's surprisingly good and works more often than not. (The commercial use we were putting it to: part of a compiler chain for the red button functionality on satellite TV. Remember: if you're selling crufty proprietary vertical market software for $10k/seat/year, always put "Open" in the name.) I realise this is anecdote wars, but nevertheless it'd be interesting to know where it falls down.
  - cookiecaper 10y ago
    WINE works very well for most software that primarily utilizes common and mature APIs, which covers a lot of really great software, especially small, specialized utilities for niches that don't get a ton of commercial attention. It's generally the more complex and cutting-edge stuff that makes use of newer pieces of .NET, DirectX, or rarely-used components of obscure APIs that WINE struggles with. Unfortunately, a large amount of the interesting Windows-only software incorporates some of that stuff in one way or another. That's especially the case with games, which usually require very specific hand-optimization that invokes a lot of tricks. Then, to improve performance on AAA releases, driver vendors release updates that stack hacks-on-hacks. That makes gaming pretty tricky to successfully execute at performance-parity in WINE. I don't mean any of this critically, just addressing the issue. It's absolutely amazing what Alexandre et al have done so far. WINE is one of the most impressive software projects in the world, IMO. I was lucky enough to be able to contribute to it in a small way myself (patches to a prior generation of the audio engine). For many years I refused to play any game that didn't run well in WINE. Just this May, after 10 years on Linux desktop full-time, I switched back to a Windows desktop to get native performance out of my photography pipeline -- VMs just weren't cutting it, and WINE was a long way off from good support. Definitely a sad thing for me on a personal level.
    - davidgerard 10y ago
      > It's generally the more complex and cutting-edge stuff that makes use of newer pieces of .NET, DirectX, or rarely-used components of obscure APIs that WINE struggles with. Yeah, this is why Wine tends to use the "get the application to work" method. Thankfully a lotta the guys at Codeweavers are gamers who want their stuff to work too ;-) .NET is a friggin' nightmare IME, even after you've installed over half a gigabyte of Microsoft downloads.
      - brianwawok 10y ago
        Net should get better over time with native Linux support no?
        JetSpiegel 10y ago
jhasse 10y ago
Hm ... Wine 1.8 also had a code freeze: http://www.phoronix.com/scan.php?page=news_item&px=Wine-1.8-Code-Freeze http://www.phoronix.com/scan.php?page=news_item&px=Wine-1.8-...
- makomk 10y ago
  Every even-numbered Wine release is a stable release preceded by a code freeze. If they followed the normal pattern, this release would be Wine 1.10.
saurik 10y ago
From the wording, which I only point out as it seems like people reading your comment are being confused and maybe that means you are also confused, this is a standard code freeze for this one release: the idea being that on your way to a release, such as 2.0 (or 1.8), at some point you have to say "look, we are doing a release here, stop making major changes so we can fix some bugs and cut a version", and this "release candidate" "marks the beginning of the code freeze period" (implicitly for the release of 2.0).
deleted 10y ago
[deleted]

sp332 10y ago

According to the description of the WineConf keynote on this page, https://www.winehq.org/wwn/403 https://www.winehq.org/wwn/403 they're just switching to time-based releases. The mobile version of that page was broken for me, but switching to the desktop version helped.