canmove, Confirmed users
1,953
edits
Engagement/MDN Durable Team/Processes/Content issue triage process: Difference between revisions
Engagement/MDN Durable Team/Processes/Content issue triage process (view source)
Revision as of 22:39, 24 April 2019
, 24 April 2019no edit summary
(Migrate content from Gdoc) |
No edit summary |
||
| Line 24: | Line 24: | ||
== Additional process for the final triage meeting of each sprint == | == Additional process for the final triage meeting of each sprint == | ||
During week that a sprint ends, and planning occurs for the next sprint: | During week that a sprint ends, and planning occurs for the next sprint: | ||
# Look through the P2 bugs list, starting with the oldest ones first, and promote a maximum of (2 * # of team members) to P1. | # Look through the P2 bugs list, starting with the oldest ones first, and promote a maximum of (2 * # of full-time team members) to P1. | ||
#* While P2 bugs still exist in Bugzilla, review those first, and migrate to GitHub when they are promoted to P1. | #* While P2 bugs still exist in Bugzilla, review those first, and migrate to GitHub when they are promoted to P1. | ||
# Close any P2 bugs that are no longer relevant. | # Close any P2 bugs that are no longer relevant. | ||
| Line 30: | Line 30: | ||
# If you ever run out of P2s, go onto P3s, etc., being sure to review both Bugzilla and GitHub for potential issues to promote. | # If you ever run out of P2s, go onto P3s, etc., being sure to review both Bugzilla and GitHub for potential issues to promote. | ||
Maximum number of P1s allowed: (4 * # of team members) --- 2 per writer for the current sprint, and for the upcoming sprint. | Maximum number of P1s allowed: (4 * # of full-time team members) --- 2 per writer for the current sprint, and for the upcoming sprint. | ||
= Helpful links = | = Helpful links = | ||