canmove, Confirmed users, Bureaucrats and Sysops emeriti
2,776
edits
Security Severity Ratings: Difference between revisions
Jump to navigation
Jump to search
→Additional Status Codes or Whiteboard Tracking Tags
| Line 229: | Line 229: | ||
! style="width:5%" | Examples | ! style="width:5%" | Examples | ||
|- | |- | ||
|<b>sec-assigned:UserAlias</b> | |<strike><b>sec-assigned:UserAlias</b></strike> <b>depricated for sec-review? flag with alias</b> | ||
|This designates the assigned security resource that is accountable for actions to be taken on the designated item. When possible the bug will be assigned to the security contact for action. This will be used when that is not possible or practical. | |This designates the assigned security resource that is accountable for actions to be taken on the designated item. When possible the bug will be assigned to the security contact for action. This will be used when that is not possible or practical. | ||
| | |sec-review?:curtisk@blah.bah indicates that curtisk is the accountable party for action | ||
|- | |- | ||
|<b>[Q2]</b> | |<b>[Q2]</b> | ||
| Line 248: | Line 248: | ||
|This designates a bug as being a critical bug for the efforts around our mobile browser project. This could be combined with either the [k9o] or [basecamp] tags as a bug could be part of both. | |This designates a bug as being a critical bug for the efforts around our mobile browser project. This could be combined with either the [k9o] or [basecamp] tags as a bug could be part of both. | ||
| | | | ||
|- | |||
|<b>[triage needed]</b> | |||
|Used to mark a bug for weekly triage meeting. | |||
| | |||
|- | |||
|<b>[pending secreview]</b> | |||
| Indicates a secreview or tasks related to said review are yet to be completed. | |||
| | |||
|- | |||
|<b>[start mm/dd/yyyy][target mm/dd/yyyy]</b> | |||
|This indicates that expected dates to start and complete work on a given review or security bug. | |||
|[start 01/29/2013][target 02/09/2013] indicates work will start on 29-Jan and expected target for completion on 09-Feb | |||
|- | |||
|<b>[completed secreview]</b> | |||
| Indicates the given secreivew or related tasks have been completed | |||
| | |||
|- | |||
|<b>mentorship</b> | |||
| Indicates that a given bug is part of our security mentorship program. The assignee of said bug is the Mozilla mentor for such a bug. | |||
| | |||
|- | |||
|<b>[score:##] | |||
|This indicates the relative severity score for risk rating bugs per the calculator at https://people.mozilla.com/~ckoenig/ | |||
|[score:30:moderate] shows that the issue has a numerical score of 30 and a severity of moderate. | |||
|- | |- | ||
|} | |} | ||