On Fri, Apr 18, 2008 at 05:59:16PM +0200, Alexandre Julliard wrote:
... Bugs fixed since 0.9.59: ... 7174 Master of Orion 2 does not switch screen resolution correctly ...
That this bug is listed as "fixed since 0.9.59" is wrong, and it sounds as if you wrongly count all bugs closed since 0.9.59 as having been present in 0.9.59?
Looking through some of the other bugs (especially older ones) the information in Bugzilla indicates for several other bugs listed in your announcement that they were not "fixed since 0.9.59".
You Wine developers are doing a great job, but especially since you are currently actively triaging older bugs "fixed since 0.9.59" is quite different from "closed since 0.9.59".
Alexandre Julliard
cu Adrian
Adrian Bunk bunk@stusta.de writes:
That this bug is listed as "fixed since 0.9.59" is wrong, and it sounds as if you wrongly count all bugs closed since 0.9.59 as having been present in 0.9.59?
Looking through some of the other bugs (especially older ones) the information in Bugzilla indicates for several other bugs listed in your announcement that they were not "fixed since 0.9.59".
You Wine developers are doing a great job, but especially since you are currently actively triaging older bugs "fixed since 0.9.59" is quite different from "closed since 0.9.59".
Not really; the important point is that the bug is not present in 0.9.60. I don't think it matters all that much to know whether it was really still present in 0.9.59, or already fixed there but not reported as such.
Doing this right would require adding support in bugzilla for storing the sha1 of the commit that fixed the bug, then we could query exactly which release fixed which bug. Patches are welcome...
On Fri, Apr 18, 2008 at 07:46:51PM +0200, Alexandre Julliard wrote:
Adrian Bunk bunk@stusta.de writes:
That this bug is listed as "fixed since 0.9.59" is wrong, and it sounds as if you wrongly count all bugs closed since 0.9.59 as having been present in 0.9.59?
Looking through some of the other bugs (especially older ones) the information in Bugzilla indicates for several other bugs listed in your announcement that they were not "fixed since 0.9.59".
You Wine developers are doing a great job, but especially since you are currently actively triaging older bugs "fixed since 0.9.59" is quite different from "closed since 0.9.59".
Not really; the important point is that the bug is not present in 0.9.60. I don't think it matters all that much to know whether it was really still present in 0.9.59, or already fixed there but not reported as such.
I might be a bit nitpicking, but "Bugs fixed since 0.9.59" implies for me that these bugs have been fixed after 0.9.59.
And when I'm reading the 0.9.60 announcement I'm mostly interested in whether upgrading from 0.9.59 to 0.9.60 is worth it, not whether your Bugzilla triage has found that a bug has been fixed a year ago. [1]
Doing this right would require adding support in bugzilla for storing the sha1 of the commit that fixed the bug, then we could query exactly which release fixed which bug. Patches are welcome...
Without any patches you could add fields "Known to work:" and "Known to fail:" as in the gcc Bugzilla (see e.g. [2]), when resolving a bug updating them, and then query for which bugs 0.9.59 was known to fail and 0.9.60 is known to work.
Alexandre Julliard
cu Adrian
[1] triaging bugs is an important task, but the information about closing bugs fixed long ago doesn't belong here [2] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20623
Adrian Bunk bunk@stusta.de writes:
I might be a bit nitpicking, but "Bugs fixed since 0.9.59" implies for me that these bugs have been fixed after 0.9.59.
I can certainly change it to "Bugs fixed in 0.9.60" if you prefer that.
And when I'm reading the 0.9.60 announcement I'm mostly interested in whether upgrading from 0.9.59 to 0.9.60 is worth it, not whether your Bugzilla triage has found that a bug has been fixed a year ago. [1]
But maybe other people are interested to know that their bug has been fixed, and don't care whether it was fixed before or after 0.9.59. Since there is at the moment no good way to find out which bugs were fixed in 0.9.59 but marked resolved after that, listing them in the next announcement is IMO better than not listing them at all.
-
Adrian Bunk -
Alexandre Julliard