blob: c1884644017a535bbf500b8aaea79fcd7eb84779 [file] [log] [blame] [view]
Robert Liaoe8c49782018-12-10 21:51:521# Chromium UI Frontline Triage Procedures and Policy
2
3## Filing New Issues
4
5### Steps
6
John Palmer046f9872021-05-24 01:24:5670. Read and follow the [Chromium Code of Conduct](https://chromium.googlesource.com/chromium/src/+/main/CODE_OF_CONDUCT.md).
Robert Liaoe8c49782018-12-10 21:51:5281. File your issue on http://crbug.com/.
9 * Required: Repro Steps
10 * Preferred: Screenshots
11 * Optional: Video Repro (Please keep brief and to the point)
122. Add the label Hotlist-DesktopUIConsider.
133. Find an appropriate component.
14
15### Consideration Deadline
16Issues must be marked Hotlist-DesktopUIConsider by Wednesday 5:00p PT for
17consideration for that week.
18
19## Weekly Triage Process
201. After the consideration deadline, query for all Hotlist-DesktopUIConsider
21 bugs.
222. For each bug, perform the following:
23 1. Assess Priority
24 * P0: Emergency, must be fixed now or before the next Canary. Mark with a
25 ReleaseBlock label for the nearest build that does not have the
26 issue.
27 * P1: Bug most users will hit. Mark with a ReleaseBlock label.
28 * Mark ReleaseBlock-Dev if the issue impacts a core scenario (like
29 scrolling).
30 * Mark ReleaseBlock-Beta if the issue impacts a secondary scenario.
31 * Mark ReleaseBlock-Stable if Chrome should never ship with this issue.
32 * P2 - Bug that many users may hit and/or has a reasonable workaround.
33 * P3 - Bug that few users will hit.
34 2. Schedule a milestone.
35 3. Assign to relevant area owner:
36 * Omnibox: jdonneley@
37 * Top Chrome: dfried@
38 * UI Platform: robliao@
39 * WebUI: dpapad@
403. Once all bugs are triaged, remove the Hotlist-DesktopUIConsider label and add
41 Hotlist-DesktopUITriaged.
42
43## Periodic Review at Milestone Branch
44For all Hotlist-DesktopUITriaged bugs, reassess priority and milestone using the
45above standards.