Re: bug-buddy integration

2009-03-13 Thread Federico Mena Quintero
On Thu, 2009-03-12 at 10:21 +0100, Frederic Crozat wrote:

[Breakpad / Socorro / Crash catcher]
 Which is used in latest version of bug-buddy and known to be broken on
 build.gnome.org because nobody has time to maintain it :(

At one point bug-buddy generated a stack trace and sent it to b.g.o (or
to bugzilla.distro.org as per-distro patches).  With those stack traces,
you were either able to fix the bug, or start diagnosing it, or at least
you could tell the submitter, please install debuginfo for this
dependency as I need to see what's going on there.

Currently, bug-buddy doesn't send a stack trace, so what it sends is
useless.  In such bug reports, you must always ask the submitter,
please get a stack trace with all the trouble that explaining that
entails.

Why don't we just revert to the old version of bug-buddy?  It required
no upstream or downstream maintenance to *keep it working*, that is, to
be producing stack traces automatically.  In the new bug-buddy, the
default is it doesn't work.

  Federico

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: bug-buddy integration

2009-03-13 Thread Andre Klapper
Am Freitag, den 13.03.2009, 15:13 -0600 schrieb Federico Mena Quintero:
 Currently, bug-buddy doesn't send a stack trace

Why do you assume bug-buddy does not send a stacktrace?
My bug-buddy did send a stacktrace a few days ago, otherwise I wouldn't
have been able to submit gnome bug 575009.

 In such bug reports, you must always ask the submitter, please 
 get a stack trace with all the trouble that explaining that entails.

A stock answer linking to http://live.gnome.org/GettingTraces explaining
everything(tm) is just one click away. If that wikipage is unclear
everyone is invited to edit/improve it.

 In the new bug-buddy, the default is it doesn't work.

I can't second this.
In fact the new (whatever that means) bug-buddy has reduced bugsquad
workload by e.g. rejecting many useless traces already before they get
submitted to gnome bugzilla.

andre
-- 
 mailto:ak...@gmx.net | failed
 http://www.iomc.de/  | http://blogs.gnome.org/aklapper

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list