lubuntu-qa team mailing list archive
-
lubuntu-qa team
-
Mailing list archive
-
Message #04659
Re: QA = testing, development, and triage
On Tue, Oct 14, 2014 at 11:56 AM, Artemgy <launchpad@xxxxxxxxx> wrote:
>> On Tue, 14 Oct 2014 11:04:42 -0700 <wxl@xxxxxxxxxx> wrote:
>>>> totally missing in our quality efforts.
>>> I agree and would like to know more about triaging.
>> I guess it would be nice to have some context so others who are less
>> aware would know, so here's the official page on triage:
>> https://wiki.ubuntu.com/Bugs/Triage
> As a bug reporting noob I have found triaging pages (for the relevant
> sub-system) invaluable for improving the quality of my own reports. A
> collection of links will be a great start, and then we can gradually
> fill out Lubuntu specific triaging notes, to help anyone who creates
> reports - as well as those who join the bug squad.
By the way, if you want to be able to assign importance and mark as
triaged and/or won't fix, you need to be a member of BugControl:
https://wiki.ubuntu.com/UbuntuBugControl
Long story short on triaging as I see it:
1. Look for dupes.
2. Confirm if you can.
3. Make sure the report is complete.
4. Set status and importance.
5. Link upstream.
wxl
Follow ups
References
-
QA = testing, development, and triage
From: ∅, 2014-10-14
-
Re: QA = testing, development, and triage
From: Brendan Perrine, 2014-10-14
-
Re: QA = testing, development, and triage
From: ∅, 2014-10-14
-
Re: QA = testing, development, and triage
From: Artemgy, 2014-10-14