Wine 0.9.58
RSS feed
Email alert
You must sign up or login to contribute to the APC forums
is writing, writing and writing
APC staff
21 posts
Posted: 22/03/2008 8:03 PM
|
A new version of Wine (0.9.58) has just come out!
The list of changes and bug fixes is quite extensive (World of Warcraft, Adobe Flash CS3, WinMerge, diff in Dreamweaver 8 crash fixes!).
Has anyone tried it already? Any early impressions?
|
|
permalink
Digg
Slashdot
send to a friend
|
The bleading edge is very sharp!
User
27 posts
Posted: 30/03/2008 11:03 AM
|
No but i hope its better than the last version i tried...
|
|
permalink
Digg
Slashdot
send to a friend
|
User
8 posts
Posted: 15/05/2008 6:05 PM
|
I can't help but feel that Wine is being supplanted by VM apps. Seems to be more talk about Virtual Box, VMWare and Parallels than good ol Wine.
|
|
permalink
Digg
Slashdot
send to a friend
|
Regular user
59 posts
Posted: 19/07/2008 3:07 PM
|
Wine isn't perfect but it adds some functionality to a computer and is a useful tool in fufiling its intended role.
|
|
permalink
Digg
Slashdot
send to a friend
|
New user
1 posts
Posted: 13/08/2008 6:08 PM
|
i have a full version of worlds oldest wine
Wine Club
|
|
permalink
Digg
Slashdot
send to a friend
|
New user
1 posts
Posted: 19/08/2008 8:08 PM
|
Wine 1.2 will come out some time in the distant future. We still don't know what will prompt us to start the stabilization process.
Some options:
* Time based release. We stabilize around the same time a major project like x.org or Gnome does, so that distributions based on their release cycles can have not only the newest desktop environment, but also the newest Wine.
* Feature based release. We label some nice to have features as 1.2 targets and then don't stabilize until "enough" of them are done.
* "1.0 is too old release." We stabilize because it becomes too much work backporting fixes to the current stable branch due to the increasing difference between the stable and development branch.
If we take too long, distros might start having to do some of their own release-management work themselves in order to get a fairly current Wine. This duplicates work, and if not done properly users will end up with different, unstable versions of Wine.
On the other hand if we release too often, we might be in code freeze longer than developers working on new experimental features would like. Continuing a separate development branch while the code freeze is in effect is one way around this, however it may result in extra work for Alexandre.
there is link for it
Wine Club
|
|
permalink
Digg
Slashdot
send to a friend
|
New user
2 posts
Posted: 10/10/2009 11:10 AM
|
The code freeze will be less rigid at first, but we're
serious about not destabilizing Wine at this point.
So go ahead and post your patches, but make sure
you've got your ducks in a row, and don't be surprised
if Alexandre pushes back.
payday loans and cash advance
|
|
permalink
Digg
Slashdot
send to a friend
|