How close are we to release? Maybe it'd be worth it to publicise the upcoming wine release by flogging rc3 in various news sites and getting more people to look for regressions.
The thread about Wylda's statistics reminded me about http://wiki.winehq.org/PlatinumRegressionHunt We mentioned that in the first 1.0 rc announcement: http://www.winehq.org/announce/1.0-rc1 but not in http://www.winehq.org/announce/1.2-rc1 How 'bout we mention it in the rc4 release announcement and/or blogs?
Dan Kegel wrote:
How close are we to release? Maybe it'd be worth it to publicise the upcoming wine release by flogging rc3 in various news sites and getting more people to look for regressions.
+1. I'm getting a fresh git and fixing/running and then submitting the EM_FORMATRANGE patches today.
James McKenzie
On Sun, Jun 13, 2010 at 10:00 AM, James McKenzie jjmckenzie51@earthlink.net wrote:
How close are we to release? Maybe it'd be worth it to publicise the upcoming wine release by flogging rc3 in various news sites and getting more people to look for regressions.
+1.
OK, I've posted something to linuxtoday and lwn.net. I wanted to include something about how many bugs have been fixed etc., but I didn't have those statistics handy, so I just said "many more apps should work with 1.2 than with 1.0".
I'm getting a fresh git and fixing/running and then submitting the EM_FORMATRANGE patches today.
Thanks! - Dan
Nikolay Sivov wrote:
... it would be nice to have valgrind tests logs as you did some months ago. I think it's possible to catch something new that is easy to fix for 1.2.
You're right. I'll try to find them time to fire that up again.
How about 64 bit packages with Wow64 ? This feature is described as a major one for Wine release 1.2, but as far as I know no x86_64 package was released yet. I've been using it since release 1.1.44 for testing purposes and it seems pretty stable. If there are no objections, I'll upload i486 and x86_64 packages and announce it in Slackaware related communities asking for reviews / regressions.
Bye Simone
On Sun, Jun 13, 2010 at 10:00 AM, James McKenzie jjmckenzie51@earthlink.net wrote:
How close are we to release? Maybe it'd be worth it to publicise the upcoming wine release by flogging rc3 in various news sites and getting more people to look for regressions.
+1.
OK, I've posted something to linuxtoday and lwn.net. I wanted to include something about how many bugs have been fixed etc., but I didn't have those statistics handy, so I just said "many more apps should work with 1.2 than with 1.0".
I'm getting a fresh git and fixing/running and then submitting the EM_FORMATRANGE patches today.
Thanks!
- Dan
On Mon, Jun 14, 2010 at 08:02:08PM +0200, Ing. Simone. Giustetti wrote:
How about 64 bit packages with Wow64 ? This feature is described as a major one for Wine release 1.2, but as far as I know no x86_64 package was released yet. I've been using it since release 1.1.44 for testing purposes and it seems pretty stable. If there are no objections, I'll upload i486 and x86_64 packages and announce it in Slackaware related communities asking for reviews / regressions.
openSUSE Factory which will become openSUSE 11.3 contains this setup already.
While 11.3 is in betatesting, which might mean less bugreports, I have not heard of any yet.
Ciao, Marcus
On 06/14/2010 11:02 AM, Ing. Simone. Giustetti wrote:
How about 64 bit packages with Wow64 ? This feature is described as a major one for Wine release 1.2, but as far as I know no x86_64 package was released yet. I've been using it since release 1.1.44 for testing purposes and it seems pretty stable. If there are no objections, I'll upload i486 and x86_64 packages and announce it in Slackaware related communities asking for reviews / regressions.
On the Ubuntu side this isn't going to happen until Maverick due to changes in the underlying handling of 64-bit libraries. Or, put differently, it's too big a change for a stable release update of Wine in Lucid (1.2 will be fit for stable release update, however, exactly because of all this regression-fixing we're doing).
Thanks, Scott Ritchie
On Mon, Jun 14, 2010 at 12:53 AM, Dan Kegel dank@kegel.com wrote:
How close are we to release? Maybe it'd be worth it to publicise the upcoming wine release by flogging rc3 in various news sites and getting more people to look for regressions.
If it's still a couple of weeks off I could write up a request to put in WWN for people to fire up Wine and test their favourite apps. I've just finished my last grueling assignment set for the semester so I want to get on to putting out another WWN on the road to release. Regardless I'll try and have some thing out for this friday.
Edward Savage wrote:
On Mon, Jun 14, 2010 at 12:53 AM, Dan Kegel dank@kegel.com wrote:
How close are we to release? Maybe it'd be worth it to publicise the upcoming wine release by flogging rc3 in various news sites and getting more people to look for regressions.
If it's still a couple of weeks off I could write up a request to put in WWN for people to fire up Wine and test their favourite apps. I've just finished my last grueling assignment set for the semester so I want to get on to putting out another WWN on the road to release. Regardless I'll try and have some thing out for this friday.
Great idea and good luck on finishing another semester of school. Hopefully, your grades were good and you learned a lot.
James McKenzie
On 6/13/2010 18:53, Dan Kegel wrote:
How close are we to release?
Not closely related to a beta testing, but for quality it is - it would be nice to have valgrind tests logs as you did some months ago. I think it's possible to catch something new that is easy to fix for 1.2.
Nikolay Sivov nsivov@codeweavers.com writes:
On 6/13/2010 18:53, Dan Kegel wrote:
How close are we to release?
Not closely related to a beta testing, but for quality it is - it would be nice to have valgrind tests logs as you did some months ago. I think it's possible to catch something new that is easy to fix for 1.2.
It's a little late for that. At this point we need to concentrate on bugs that affect real applications, and preferably regressions.
-
Alexandre Julliard -
Dan Kegel -
Edward Savage -
Ing. Simone. Giustetti -
James McKenzie -
Marcus Meissner -
Nikolay Sivov -
Scott Ritchie