313
edits
Platform/JS: Difference between revisions
→JS Bug Triage Tags
| Line 10: | Line 10: | ||
** expected to be about 20-30 bugs per cycle | ** expected to be about 20-30 bugs per cycle | ||
*** need to follow up to make sure we're not getting too perfectionistic | *** need to follow up to make sure we're not getting too perfectionistic | ||
* p2 = "want to do" | |||
** examples: high-value feature work, medium user-facing defects | |||
* p3 = "may do" | |||
** examples: minor user-facing defects, minor spec violations | |||
'''[js:pX]''' A bug of priority X, not currently targeted for any particular fix time. | |||
'''[js:inv:pX]''' A bug that needs deeper technical investigation before it can be fully triaged, where the investigation has priority X. This priority is not clearly defined yet. For now, it can be considered a guess at what the priority will be after investigation. After investigation, the bug should be assigned a new triage tag. | |||
'''[js:waitingforinfo]''' We need more information before we can do anything with the bug. | |||
'''[js:nonactionable]''' There is no way to make progress on the bug. | |||
'''[js:t]''' 't' for 'triaged'. This is used for bugs that don't need a priority or other tag assigned. The majority of bugs will actually be in this category because they are filed by JS team members and fuzz testers and can be handled internally without a triage process. | |||
'''[js:wait YYYY-MM-DD]''' There is nothing to do until the given date is reached. | |||
'''[js:dm][js:ni]''' Initials of the person following up on the bug. Not all bugs need this--it's mostly if one person wants to indicate they need to do something with it. | |||