canmove, Confirmed users
737
edits
Jetpack/Triage Process: Difference between revisions
no edit summary
No edit summary |
|||
| Line 13: | Line 13: | ||
If more information is required to decide on priority the bug will be left unprioritised, [triage:followup] will be added to the whiteboard and the bug will be assigned to the SDK engineer who is in charge of finding answers to questions that the triage team have (this may involve wrangling answers from the reporter, attempting to reproduce, etc.). Once the engineer has answered the questions they may unassign themselves from the bug if they don't intend to continue and fix it at that time. Every week the triage team will re-visit the bug to see if a decision can be made about the bug's priority. | If more information is required to decide on priority the bug will be left unprioritised, [triage:followup] will be added to the whiteboard and the bug will be assigned to the SDK engineer who is in charge of finding answers to questions that the triage team have (this may involve wrangling answers from the reporter, attempting to reproduce, etc.). Once the engineer has answered the questions they may unassign themselves from the bug if they don't intend to continue and fix it at that time. Every week the triage team will re-visit the bug to see if a decision can be made about the bug's priority. | ||
If the triage team thinks that the bug should be mentioned in the release notes for the version in which it is fixed, they should add the "relnote-needed" keyword to the bug. Fixes that should be mentioned in release notes are those that change the current behavior of the SDK in a way that would surprise or confuse add-on developers (i.e. not just fixing something that is broken, but changing something to work in a different way) or those that add substantial new features that add-on developer might want to take advantage of. | |||
=== Attending Triage === | === Attending Triage === | ||