10
edits
Security/Firefox/Security Bug Escalation Process: Difference between revisions
Jump to navigation
Jump to search
Security/Firefox/Security Bug Escalation Process (view source)
Revision as of 02:12, 25 January 2018
, 25 January 2018no edit summary
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
## Roles of stakeholders: | ## Roles of stakeholders: | ||
##* Driver: Wennie Leung | ##* Driver: Wennie Leung | ||
##* Approvers: Dan Veditz, Wennie Leung, Release owner of a relevant release (rotating) | ##* Approvers for uplift and exception: Dan Veditz, Wennie Leung, Release owner of a relevant release (rotating) | ||
##* Consult/Contributor: Marshall Erwin, Director of Trust and Safety; Emma Humphries, Bugmaster. | ##* Consult/Contributor: Marshall Erwin, Director of Trust and Safety; Emma Humphries, Bugmaster. | ||
##* Informed: Engineering Directors: Selena Deckelmann, Joe Hildebrand, Chris Karloff | ##* Informed: Engineering Directors: Selena Deckelmann, Joe Hildebrand, Chris Karloff | ||
| Line 15: | Line 15: | ||
##* Determine the list of security bugs can be shipped with the release without compromising its security and quality. | ##* Determine the list of security bugs can be shipped with the release without compromising its security and quality. | ||
#Escalation path | #Escalation path | ||
#* In the event that agreement cannot be reached by the sec bug stakeholders, issues will be escalated to Sr Director of Engineering, Dave Camp and SVP of Firefox Mark Mayo for a decision. | #* In the event that agreement cannot be reached by the sec bug stakeholders, issues will be escalated to Sr Director of Engineering, Dave Camp and Sr Director of Product Integrity, Yan Or. | ||
#* In the event that agreement again cannot be reached, the issue will escalate to SVP of Firefox Mark Mayo for a final decision. | |||
#Uplifting security bug fixes across the train releases | |||
#* Security uplift nominations a week before go-live will be reviewed by security team and release owner for feasibility to include in m-r, esr branch. | |||
#* Security uplift nominations from start of beta cycle up to the week before RC week will be reviewed by release owner. Typically, sec-high and sec-crit uplifts are approved for landing to beta and ESR branch. | |||