dropping bug-buddy reports for old version of gnome automatically
Hi, in the last months the bugzilla traffic has risen exponentially because of (thanks to?) the new bug-buddy which actually manages to submit a higher percentage of the crashes. This has some very good effects (since not only we get most of the bugreports, but we also have statistics telling us which are the most common bugs) but it also causes a very high traffic for people who get bugzilla mail and a huge amount of work for bug triagers. Personally I am not able anymore to handle my bugmail anymore and even useful bugreports get lost in the noise. As a first step, what do you think of just dropping silently at least crash reports from older versions of gnome? All bugs coming from there are either already fixed or will be reported anyway if still present in newer versions. This was not much of an issue until now since the old versions of gnome used the old bug buddy, but this will change soon... As far as I am concerned I'd like to drop any reports from 2.16 and below, but I see how that may be a little to aggressive. What about dropping reports from 2.14 and below? ciao Paolo ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: dropping bug-buddy reports for old version of gnome automatically
On 07/04/07 16:13, Paolo Borelli wrote: Hi, [...] Personally I am not able anymore to handle my bugmail anymore and even useful bugreports get lost in the noise. I usually mark any Crash: ... bugmail as read without even looking at it nowadays. As a first step, what do you think of just dropping silently at least crash reports from older versions of gnome? All bugs coming from there are either already fixed or will be reported anyway if still present in newer versions. Is there any way to do it non-silently? There needs to be something to at least inform the user they have an ancient version of GNOME and should consider upgrading. Regards, Thomas ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: dropping bug-buddy reports for old version of gnome automatically
On Sat, 2007-04-07 at 17:13 +0200, Paolo Borelli wrote: Personally I am not able anymore to handle my bugmail anymore and even useful bugreports get lost in the noise. Tell me about it. gnome-power-manager 2.18.0 had a bug where it would segfault when you locked the screen if HAL was not running. 2.18.1 fixed the bug, but that still means I get about 5-10 duplicate bugzillas a day. The guys triaging this stuff have been great, but it's still more and more emails for me. I'm really thinking the auto-submit thing to bugzilla should have more text like: 1. You do not have debuginfo packages installed, the trace may not be useful to the developer. 2. [click here to check to see if the crash was already reported] 3. You are running an old version. This crash may be fixed in newer versions of the product. Point 1 assumes we can tell what useful debuginfo packages should be installed for each package. Point 2 assumes we can automatically check for similar stacktraces. Point 3 assumes the bugbuddy can query the servers for the latest version. I'm sure other maintainers must be getting as demoralised as myself when dealing with so many duplicates of a fixed bug. Richard. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: dropping bug-buddy reports for old version of gnome automatically
Richard Hughes wrote: On Sat, 2007-04-07 at 17:13 +0200, Paolo Borelli wrote: Personally I am not able anymore to handle my bugmail anymore and even useful bugreports get lost in the noise. Tell me about it. gnome-power-manager 2.18.0 had a bug where it would segfault when you locked the screen if HAL was not running. 2.18.1 fixed the bug, but that still means I get about 5-10 duplicate bugzillas a day. The guys triaging this stuff have been great, but it's still more and more emails for me. We can auto reject specific stack traces [1] for this very reason. Get in touch with your local bugsquadder/bugmaster for more information. I'm really thinking the auto-submit thing to bugzilla should have more text like: 1. You do not have debuginfo packages installed, the trace may not be useful to the developer. This happens [2] if we manage to detect it.. Thanks, Andrew [1] http://blogs.gnome.org/view/ovitters/2006/11/12/0 [2] http://blogs.gnome.org/view/ovitters/2007/01/06/0 ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: dropping bug-buddy reports for old version of gnome automatically
[Just noticed that Andrew made most of my email obsolete before I finished. Maybe you'll see something useful, though, so I'll still send it.] On 4/7/07, Richard Hughes [EMAIL PROTECTED] wrote: On Sat, 2007-04-07 at 17:13 +0200, Paolo Borelli wrote: Personally I am not able anymore to handle my bugmail anymore and even useful bugreports get lost in the noise. Tell me about it. gnome-power-manager 2.18.0 had a bug where it would segfault when you locked the screen if HAL was not running. 2.18.1 fixed the bug, but that still means I get about 5-10 duplicate bugzillas a day. The guys triaging this stuff have been great, but it's still more and more emails for me. You can have such bugs automatically rejected with a specialized notice (Thanks for the bug report, but this issue has been fixed in gnome-power-manager 2.18.1; please update your software.) One example is bug 352592 which has had over 3000 duplicates automatically rejected[1]. See http://live.gnome.org/Bugsquad/AutoReject for more details. I believe Olav set the system up so that only a few users (maybe 3 or 4?) had permissions to add bugs to the auto-reject list, so you'll probably need to email the bugsquad to ask someone to do it for you. I'm really thinking the auto-submit thing to bugzilla should have more text like: 1. You do not have debuginfo packages installed, the trace may not be useful to the developer. http://live.gnome.org/ImprovingDebugging 2. [click here to check to see if the crash was already reported] We have no fail proof method for determining if two bugs are indeed a duplicate. Having that would be great, but we simply don't have it. Help welcome (Olav may already be working on it, so ask him first instead of starting from scratch.) 3. You are running an old version. This crash may be fixed in newer versions of the product. Rejecting on age would need to be product-specific, as which versions to reject probably depends on the volume of email the product receives. We've asked maintainers if they wanted to have bugsquadders automatically close bugs if against versions that are too old and what too old meant for their product, so moving that logic into bugzilla itself seems like a reasonable enhancement. Default would be to not reject anything based on version, of course. Point 1 assumes we can tell what useful debuginfo packages should be installed for each package. Point 2 assumes we can automatically check for similar stacktraces. Point 3 assumes the bugbuddy can query the servers for the latest version. I'm sure other maintainers must be getting as demoralised as myself when dealing with so many duplicates of a fixed bug. [1] I suggest only doing this for fixed bugs, where further reports won't be helpful; otherwise, you miss out on potential extra details that future bug submitters might provide. Hope that helps, Elijah ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
