tpreitzel wrote:
James Mckenzie wrote:
James:
This week. That's all, unless a serious bug is found, this is the LAST RC. AJ plans on releasing next week. We have to pick a time and that is the one he picked (read the Announcement.)
That means that you have to get really busy or convince him that there is a real good reason to hold the release (like some really popular game/productivity program does not function at all or an important function is not working.)
I have two patches that are waiting for release as well. These affect many programs. Thay should have been in 1.2, but did not make it.
I'll have to get 'busy' myself this weekend and get the programs I support tested and updated.
James McKenzie
-----Original Message-----
From: James_Huk <wineforum-user@xxxxxxxxxx>
Sent: Jul 9, 2010 1:44 PM
To: wine-users@xxxxxxxxxx
Subject: Re: How many more RCs are you planning before wine-1.2?
No problem - I am not pushing anyone ;]
I asked because I wanted to know how much time is left for testing existing bugs with current RCs (there are probably many bugs that are resolved already and just needs to be retested and closed)
However now I am a bit confused - @eps do you mean that there will be about 8 more RCs (assuming 4 RCs per month) or that @dimesio is right, and today's release will be the last one, and we will have to wait for two months before next (stable wine-1.2) release?
Frankly, there's plenty of good reasons for holding the release of WINE 1.2.
The FACT that many applications (games) are suddenly losing the audio after several minutes of play and then crashing to the desktop shortly thereafter is a pretty good reason for holding the release of WINE 1.2.
Repeatable example?
Most of the problems are caused by pulseaudio crashing, not Wine, BTW.
The driver may not fail, but it is causing Wine to crash. That is not a
Wine problem but a poor implemenation of an unneeded driver.
James McKenzie
