Tom Wickline wrote:
http://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW...
Three releases to fix 88 nasty bugs?
The sad fact is that it would take a lot more than that to fix them all, and it probably doesn't make sense to hold up the release until it's perfect.
We probably want to update http://wiki.winehq.org/WineReleaseCriteria with the current release criteria.
Some other interesting searches:
Bugs marked as 'regression' (340!): http://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW...
Bugs marked 'bisected': http://bugs.winehq.org/buglist.cgi?quicksearch=bisected
Anything A.F. has analyzed : http://bugs.winehq.org/buglist.cgi?product=Wine&bug_status=UNCONFIRMED&a... - Dan
On Sun, May 9, 2010 at 7:02 AM, Dan Kegel dank@kegel.com wrote:
Tom Wickline wrote:
http://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW...
Three releases to fix 88 nasty bugs?
The sad fact is that it would take a lot more than that to fix them all, and it probably doesn't make sense to hold up the release until it's perfect.
We probably want to update http://wiki.winehq.org/WineReleaseCriteria with the current release criteria.
Some other interesting searches:
Bugs marked as 'regression' (340!):
http://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW...
Bugs marked 'bisected': http://bugs.winehq.org/buglist.cgi?quicksearch=bisected
Anything A.F. has analyzed :
http://bugs.winehq.org/buglist.cgi?product=Wine&bug_status=UNCONFIRMED&a...
- Dan
I thought the code freeze, RC cycle would be more like three months not
three releases, e.g six weeks. But I'm 100% sure AJ knows best. :)
-- Tom
Tom Wickline twickline@gmail.com writes:
I thought the code freeze, RC cycle would be more like three months not three releases, e.g six weeks. But I'm 100% sure AJ knows best. :)
Nobody said it can't be three months. It will last as long as good fixes keep pouring in. In practice after 1-2 months we usually run out of bugs that can be reasonably fixed; at that point it wouldn't make sense to hold the release for another month to get 3 extra fixes.
And like last time, I'm planning to make rc releases on a weekly schedule, so we should get plenty of them.
While we're linking to bug lists, this one seems most interesting to me: http://bit.ly/bfOHK5
That's the list of major regressions introduced since 1.0-rc1.
Bug 13891 in particular will make us look bad if it's not fixed before 1.2. A lot of apps (as I understand it, any app that does it properly) can't open url's anymore in the native browser, and this worked in 1.0.
Vincent Povirk wrote:
While we're linking to bug lists, this one seems most interesting to me: http://bit.ly/bfOHK5
That's the list of major regressions introduced since 1.0-rc1.
Bug 13891 in particular will make us look bad if it's not fixed before 1.2. A lot of apps (as I understand it, any app that does it properly) can't open url's anymore in the native browser, and this worked in 1.0.
Vincent:
+1. This is will be reported again and again.
James McKenzie
Vincent Povirk wrote:
While we're linking to bug lists, this one seems most interesting to me: http://bit.ly/bfOHK5
That's the list of major regressions introduced since 1.0-rc1.
Bug 13891 in particular will make us look bad if it's not fixed before 1.2. A lot of apps (as I understand it, any app that does it properly) can't open url's anymore in the native browser, and this worked in 1.0.
Actually, when I read through the report, it broke in 1.0-rc4 but worked in 0.9.52. That is one old bug and aggravating too.
James McKenzie
Actually, when I read through the report, it broke in 1.0-rc4 but worked in 0.9.52. That is one old bug and aggravating too.
You're right, so it didn't work in 1.0.
That's.. that might actually be worse.
Vincent Povirk wrote:
Actually, when I read through the report, it broke in 1.0-rc4 but worked in 0.9.52. That is one old bug and aggravating too.
You're right, so it didn't work in 1.0.
That's.. that might actually be worse.
Vincent:
This should be on the 1.2 todo list. This really needs to be fixed and is/was the topic of a thread on the Wine-Users list recently.
James McKenzie
On Sat, May 8, 2010 at 7:16 PM, Vincent Povirk madewokherd@gmail.comwrote:
While we're linking to bug lists, this one seems most interesting to me: http://bit.ly/bfOHK5
That's the list of major regressions introduced since 1.0-rc1. ...
What criteria did you use to build that list? There's a bunch of recent breakage in cursor support that make a lot of games very difficult to use.
Erich Hoover ehoover@mines.edu
On Sat, May 8, 2010 at 8:43 PM, Erich Hoover ehoover@mines.edu wrote:
On Sat, May 8, 2010 at 7:16 PM, Vincent Povirk madewokherd@gmail.com wrote:
While we're linking to bug lists, this one seems most interesting to me: http://bit.ly/bfOHK5
That's the list of major regressions introduced since 1.0-rc1. ...
What criteria did you use to build that list? There's a bunch of recent breakage in cursor support that make a lot of games very difficult to use.
Version >= 1.0-rc1 Severity >= major Keywords include "regression"
-
Alexandre Julliard -
Dan Kegel -
Erich Hoover -
James McKenzie -
Tom Wickline -
Vincent Povirk