Ok, the author has posted a link to the commit.. http://www.winehq.org/hypermail/wine-cvs/2004/10/0376.html Seems to be what broke it, per regression testing. I dunno if this maybe caused a bug somewhere else to show up or what, but I figure someone could look at it..
Dustin
On Tue, 10 May 2005 21:47:24 -0500, Dustin Navea wrote:
Ok, the author has posted a link to the commit.. http://www.winehq.org/hypermail/wine-cvs/2004/10/0376.html Seems to be what broke it, per regression testing. I dunno if this maybe caused a bug somewhere else to show up or what, but I figure someone could look at it..
Dustin, your energy is admirable but if you're going to post emails about specific bugs could you at least include:
* Subject line * Who it's assigned to (if anybody) * Contents of the last comment * URL to bugzilla * Quick analysis of the problem
Right now I have no idea what any of these bugs are, and because I'm very lazy can't be bothered looked them up (already got enough bugs I know about ...)
thanks -mike
Mike Hearn wrote:
Dustin, your energy is admirable but if you're going to post emails about specific bugs could you at least include:
- Subject line
- Who it's assigned to (if anybody)
- Contents of the last comment
- URL to bugzilla
- Quick analysis of the problem
Right now I have no idea what any of these bugs are, and because I'm very lazy can't be bothered looked them up (already got enough bugs I know about ...)
thanks -mike
I was wondering if there was a better way to post them? Ill keep that in mind from now on.
Dustin
On Wed, 11 May 2005 21:11:40 -0500, Dustin Navea wrote:
I was wondering if there was a better way to post them? Ill keep that in mind from now on.
Well, I'm a bit dubious as to the value of posting bugs here anyway, we have wine-bugs for that. If it really does motivate people to work on them though then I guess it'd be OK.
thanks -mike
Mike Hearn wrote:
Well, I'm a bit dubious as to the value of posting bugs here anyway, we have wine-bugs for that. If it really does motivate people to work on them though then I guess it'd be OK.
It seems to not necessarily _motivate_ someone to work on a bug, but it does seem to get them fixed faster.. Mainly the fastest fixes are done on regressions, which is pretty much all I report here, with one exception.. See below.
The only time I actually post a bug to wine-devel is after a regression-causing patch (or the problematic code in case its not related to a patch) is found. And even then I take a look at it to see if I could come up with a solution. Believe me, there are many more bugs that are reported that dont make it to the list, simply because the user isn't willing/able to either run a regression test, or provide the necessary logs and backtrace.
Since I am a maintainer for bugzilla, I figure the more I probe the users for information, the less you will have to. And if we find the problem code, then I forward to you all, in the hopes that it can be easily fixed..
I should probably go back through the whole db looking for bugs that can be closed due to inactivity, like I started to do 4 years ago, but I havent found the time to yet. Hopefully now that all of the bugs I was working on are reported, I can do that on monday and tuesday next week, but I cant guarantee that it will happen, as something seems to always come up at the last minute. *sigh*
Either way though, I am posting a recruitment message to wine-users, because we do need some more bug competent db maintainers, which will help reduce the clutter and get bugs we need to work on priority..
Dustin
Hi,
On Thu, May 12, 2005 at 02:58:11PM +0100, Mike Hearn wrote:
On Wed, 11 May 2005 21:11:40 -0500, Dustin Navea wrote:
I was wondering if there was a better way to post them? Ill keep that in mind from now on.
Well, I'm a bit dubious as to the value of posting bugs here anyway, we have wine-bugs for that. If it really does motivate people to work on them though then I guess it'd be OK.
Many people don't subscribe to wine-bugs.
If we have a few select bugs posted here (ones that are very interesting/ important/critical/whatever), then this can only be a good thing. (as long as it does remain a moderate number of mails!)
Andreas Mohr
Andreas Mohr wrote:
Many people don't subscribe to wine-bugs.
exactly
If we have a few select bugs posted here (ones that are very interesting/ important/critical/whatever), then this can only be a good thing. (as long as it does remain a moderate number of mails!)
hehe, I was hoping someone would say that! Thanks
Dustin
Hello,
Andreas Mohr wrote:
On Thu, May 12, 2005 at 02:58:11PM +0100, Mike Hearn wrote:
On Wed, 11 May 2005 21:11:40 -0500, Dustin Navea wrote:
I was wondering if there was a better way to post them? Ill keep that in mind from now on.
Well, I'm a bit dubious as to the value of posting bugs here anyway, we have wine-bugs for that. If it really does motivate people to work on them though then I guess it'd be OK.
Many people don't subscribe to wine-bugs.
If we have a few select bugs posted here (ones that are very interesting/ important/critical/whatever), then this can only be a good thing. (as long as it does remain a moderate number of mails!)
Regressions bugs are quite interesting especialy if the culprit patch is already known
bye michael
On Thu, 12 May 2005, Mike Hearn wrote:
On Wed, 11 May 2005 21:11:40 -0500, Dustin Navea wrote:
I was wondering if there was a better way to post them? Ill keep that in mind from now on.
Well, I'm a bit dubious as to the value of posting bugs here anyway, we have wine-bugs for that. If it really does motivate people to work on them though then I guess it'd be OK.
I think if the bugs have been well diagnosed, which appears to be the case here, it can be useful to bring them to the attention of the developers: we all know that Wine developers tend to know about enough bugs already that they don't really scrub Bugzila trying to find one :-/.
But some more information directly in the email could be useful. I was not necessarily thinking about the last comment or the subject line but more:
* a more catchy subject than 'bug 2931' (which is not to say that the bug number should not be mention in the subject) * small description of the bug (so that readers at least know if it's a DirectX issue or an ntdll one, a developer working on the former would probably not be interested in bugs related to the latter) * which application is affected * URL to the bug * changelog of the patch that was identified as causing the regression * quick analysis of the problem (if possible)
With that information a developper reading only the email will know whether it's worth digging deeper and actually looking at the bug report and patch.
Also I think it's good that someone checks and cleans up Bugzilla. Dustin, keep up the good work.
-
Andreas Mohr -
Dustin Navea -
Francois Gouget -
Michael Stefaniuc -
Mike Hearn