Bug triaging

[Tymon Dąbrowski]

That's a good set of rules. I probably wouldn't add a comment if I noticed
a mismatch with OS or hardware in an issue that seems related to the OS or
hardware. Depending on the situation I might have not reported some of the
failures in reproducing bugs, too...
But I can see now how it can be useful, especially when we have so many of
those bug reports laying around untouched.




czw., 13 cze 2024 o 11:38 Halla Rempt <halla at valdyas.org> napisał(a):

> Hi,
>
> I've got a relatively good week, so I'm triaging bugs. We've got about 400
> untriaged bugs, it seems...
>
> I really would like everyone who takes a look at a bug report and tries to
> reproduce do the following:
>
> * if reproducible, confirm
> * if not, add a note of what you tried AND add the "triaged" keyword
>
> That makes it much easier to look for bugs nobody has looked at before,
> and it shows the reporter we've taken a look.
>
> If you look at a bug report and didn't try to reproduce, add a note about
> why not:
>
> * don't have access to the hardware/OS: note that
> * don't understand the bug: note that and if possible ask for
> clarification.
>
> Right now, I can only guess whether someone looked at a bug or not...
>
> Halla
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kimageshop/attachments/20240613/258d1adc/attachment.htm>