Wine 2.0 RC1 Released
winehq.org
Wine 2.0 RC1 Released
1–10 of 80 posts
Re: Wine 2.0 RC1 Released
#2Why not 1.10?
Re: Wine 2.0 RC1 Released
#3Why 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/11...
Edit: My bad. See below.
Re: Wine 2.0 RC1 Released
#4Why 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/11... Edit: My bad. See below.
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?
Re: Wine 2.0 RC1 Released
#5Why 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/11... Edit: My bad. See below.
Hm ... Wine 1.8 also had a code freeze: http://www.phoronix.com/scan.php?page=news_item&px=Wine-1.8-...
Re: Wine 2.0 RC1 Released
#6Earlier quoted context omitted.
> 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/11... Edit: My bad. See below.
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?
It could just be about breaking backwards compatibility although from a quick glance it seems more like they are signalling major milestone.
Re: Wine 2.0 RC1 Released
#7Why 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/11... Edit: My bad. See below.
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).
Re: Wine 2.0 RC1 Released
#8Earlier quoted context omitted.
> 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/11... Edit: My bad. See below.
Hm ... Wine 1.8 also had a code freeze: http://www.phoronix.com/scan.php?page=news_item&px=Wine-1.8-...
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.
Re: Wine 2.0 RC1 Released
#9Why 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/11... Edit: My bad. See below.
[deleted]
Re: Wine 2.0 RC1 Released
#10Earlier quoted context omitted.
> 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/11... Edit: My bad. See below.
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?
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.