SecurityEngineering/PSM Bug Triage: Difference between revisions

SecurityEngineering/PSM Bug Triage (view source)

Revision as of 22:26, 15 November 2017

256 bytes removed , 15 November 2017

remove outdated information, add note about P1 inactivity

Dkeeler

Confirmed users

299

edits

@@ Line 1: / Line 1: @@
 == Bug Triage in PSM ==
-PSM essentially consists of Gecko code in [https://dxr.mozilla.org/mozilla-central/source/security security/] that is not in any of the subdirectories [https://dxr.mozilla.org/mozilla-central/source/security/nss nss/], [https://dxr.mozilla.org/mozilla-central/source/security/patches patches/], or [https://dxr.mozilla.org/mozilla-central/source/security/sandbox sandbox/]. The Bugzilla product/component for PSM is [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&query_format=advanced&component=Security%3A%20PSM&product=Core Core :: Security: PSM]. Historically, many bugs related to or involving PSM have been filed in the component [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&query_format=advanced&component=Security%3A%20UI&product=Core Security: UI]. This component is going away soon, and all outstanding bugs will be moved to Security: PSM or a more appropriate place.
+PSM essentially consists of Gecko code in [https://dxr.mozilla.org/mozilla-central/source/security security/] that is not in any of the subdirectories [https://dxr.mozilla.org/mozilla-central/source/security/nss nss/], [https://dxr.mozilla.org/mozilla-central/source/security/patches patches/], or [https://dxr.mozilla.org/mozilla-central/source/security/sandbox sandbox/]. The Bugzilla product/component for PSM is [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&query_format=advanced&component=Security%3A%20PSM&product=Core Core :: Security: PSM].
-For team interoperability, PSM follows the new standardized [[Bugmasters/Process/Triage|Triage]] process. In short, every new bug should either be prioritized as P1, P2, P3, or P5, moved to a different component, or needinfo should be requested from someone. P1 means the bug should be fixed before the current Nightly branches to Aurora (and even uplifted as appropriate). P2 means the bug will be worked on "next" (basically, after P1s are taken care of). P3 means the bug is in the "should be fixed" backlog. Tracking or meta bugs are also P3. P5 is for bugs where patches would be reviewed and taken from contributors if appropriate, but otherwise won't be worked on. If a bug has had an unanswered needinfo flag for more than 2 weeks, it should be reevaluated (closing as incomplete, needinfo-ing another person, etc.).
+For team interoperability, PSM follows the new standardized [[Bugmasters/Process/Triage|Triage]] process. In short, every new bug should either be prioritized as P1, P2, P3, or P5, moved to a different component, or needinfo should be requested from someone. P1 means the bug should be fixed before the current Nightly branches to Beta (and even uplifted as appropriate). P2 means the bug will be worked on "next" (basically, after P1s are taken care of). P3 means the bug is in the "should be fixed" backlog. Tracking or meta bugs are also P3. P5 is for bugs where patches would be reviewed and taken from contributors if appropriate, but otherwise won't be worked on. If a bug has had an unanswered needinfo flag for more than 2 weeks, it should be reevaluated (closing as incomplete, needinfo-ing another person, etc.). Similarly, if a P1 bug has no activity for 2 weeks, its priority should be revisited.
 After branching, bug priorities should be revisited. If a P1 is still open, it either needs to be deprioritized (maybe it isn't really a P1) or whatever is blocking its completion needs to be identified and dealt with. P2s and P3s should be considered for promotion to a higher priority. Assignees should be found for any bugs promoted to P1.