Bjoern Michaelsen wrote on 21-09-16 18:45:
> Well, my point is if we make that an explicit requirement (e.g. "properly
> triaged bugs need to be checked for if they are crossplatform or appear on
> one") the net effects will be that devs dont yet look at the issue as it is
> properly triaged.
Sure. Now I do not support the idea that 'being proper triaged' is a
prerequisite before developers will/may look at reports.
Apart from that, the repeated example of crossplatform doesn't seem the
most exited example of proper triage to me.
Details of the reason of the bug, clear summary (finding, recognizing),
component, duplicates (may ~indicate importance) regressions (user
expectations, statistics), bibisection come to my mind much earlier.
> [...] Making every bug perfectly triaged on every
> detail before a dev sees it will waste resources, while just giving devs the
> freedom to push issues back quickly to NEEDINFO with specific details on what
> exactly they would like to know beyond basic triage makes for a much more
> targeted triage.
Sure, my point is that triage is useful for QA and devs. And indeed in a
situation that looks as if there's not really enough hands to confirm
all reports, let alone do proper triage where it would be good, let
alone to do useful clean ups and in depth investigations on certain
areas.., spending too many words on what/how the prefect route &
handling is, seems a bit superfluous ;)
So basically I don't see where we disagree :)
Ciao - Cor
GPD key ID: 0xB13480A6 - 591A 30A7 36A0 CE3C 3D28 A038 E49D 7365 B134 80A6
- vrijwilliger http://nl.libreoffice.org
- volunteer http://www.libreoffice.org
- The Document Foundation Membership Committee Member
LibreOffice mailing list