Confirmed users
978
edits
User:Hsinyi/Gecko engineering: Difference between revisions
Jump to navigation
Jump to search
→Bug triage: more contents
(→What should I work on?: new features) |
(→Bug triage: more contents) |
||
| Line 34: | Line 34: | ||
== Bug triage == | == Bug triage == | ||
Why are we doing triage? | |||
:Ensuring we don’t miss important bugs and timely actions are taken | |||
What counts as being triaged? | |||
:According to [https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html?highlight=triage%20severity|Mozilla's latest triage practice], '''severity''' field is set. | |||
What are the actions to take? | |||
:Paying particular attention to regressions | |||
:Paying particular attention for bugs impacting top websites | |||
:When needinfo someone, be clear that help is needed to try to advance it | |||
:Responding to needinfo requests and not collecting ASSIGNED bugs | |||
:Also, rotation duty of Core: General triage | |||
References: | References: | ||
| Line 40: | Line 53: | ||
[https://wiki.mozilla.org/Platform/DOM_Bug_Triage| DOM team triage] | [https://wiki.mozilla.org/Platform/DOM_Bug_Triage| DOM team triage] | ||
[https://apenwarr.ca/log/20171213| Backlog management presentation] | |||
== Code review == | == Code review == | ||
== Release health and product quality == | == Release health and product quality == | ||
== Roadmap and status communication == | == Roadmap and status communication == | ||