Confirmed users
184
edits
Security/B2G/VulnerabilityManagement: Difference between revisions
Jump to navigation
Jump to search
Security/B2G/VulnerabilityManagement (view source)
Revision as of 17:33, 10 June 2015
, 10 June 2015Whiteboard tag info and links added
(Links for Sec-Fixed-Since B2G 2.1 and Sec-No-Status B2G 2.2 updated) |
(Whiteboard tag info and links added) |
||
| Line 43: | Line 43: | ||
This Bugzilla query is intended to be '''used for automatic generation of the advisory overview''' for the Firefox 2.2 release. | This Bugzilla query is intended to be '''used for automatic generation of the advisory overview''' for the Firefox 2.2 release. | ||
== Whiteboard keywords == | |||
=== Firefox === | |||
Al Billings uses the ''[adv-*]'' tag space to declare advisory status for Firefox releases. Tags ending in ''+]'' will get an advisory, those ending in ''-]'' will not get an advisory. Generally, when there's already an ''[adv-'' tag, we don't need to care about creating an advisory for b2g, because either its already there and we must only collect it for our overview, or b2g (most likely) won't require one either. | |||
=== B2G === | |||
For Firefox OS we use ''[b2g-adv-*]'' tag space, and Al kindly asks not to pollute his ''[adv-*'' space. | |||
== Links == | |||
* [Security_Severity_Ratings] | |||