DrKonqi and BKO

[Martin Klapetek]

On Wed, Nov 2, 2016 at 6:32 AM, Harald Sitter <sitter.harald at gmail.com>
wrote:

> On Wed, Nov 2, 2016 at 11:04 AM, René J. V.  Bertin <rjvbertin at gmail.com>
> wrote:
> > Martin Klapetek wrote:
> >
> >
> >> For improving readability, there is bugzilla-traceparser plugin, that
> can
> >> dynamically
> >> hide looooooooong backtraces with a bit of JS magic to expand them and
> much
> >> more
> >> like finding duplicates and also auto-dupe. I still think this would
> help
> >> tremendously to
> >> all our bugzilla users.
> >
> > Yes, long inline backtraces do not make it easier to navigate a bug
> report.
> >
> > Still, the best thing would be a formal way to attach a backtrace, e.g.
> as an
> > attachment with a standardised name. I'm thinking of a dedicated entry
> field on
> > the bug entry webpage and programmatic hooks to upload and query these
> > attachments.
>
> Bug trackers are not trace trackers. Spending time on solving the
> actual problem is the best thing https://retrace.fedoraproject.org/
> https://errors.ubuntu.com/


They're not, yet we're using it as one. So might as well improve
the experience at least a bit.

Cheers
-- 
Martin Klapetek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20161102/a2d5152e/attachment.html>