10
edits
Security/Firefox/Security Bug Triage Process: Difference between revisions
Security/Firefox/Security Bug Triage Process (view source)
Revision as of 18:13, 30 January 2018
, 30 January 2018Update Assumptions
(Assumptions wording) |
(Update Assumptions) |
||
| Line 1: | Line 1: | ||
=== Assumptions === | === Assumptions === | ||
* We can reach the steady state of less than 10% of sec-high and sec-critical bugs that are older than 1 month by the | * We can reach the steady state of less than 10% of sec-high and sec-critical bugs that are older than 1 month by the end of Q2/2018 (steady state defined in the process below). | ||
* Security bugs that don’t affect currently shipping releases or are in features disabled behind a hidden pref don’t need to fit the same timeframe. They will, of course, need to be fixed before they’re shipped. | * Security bugs that don’t affect currently shipping releases or are in features disabled behind a hidden pref don’t need to fit the same timeframe. They will, of course, need to be fixed before they’re shipped. | ||