Security/Firefox/Security Bug Escalation Process: Difference between revisions

Security/Firefox/Security Bug Escalation Process (view source)

13 bytes added , 29 January 2018

reword uplift text

10

edits

@@ Line 18: / Line 18: @@
 #* 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 to the beta branch will be reviewed by security team and release owner within the last two weeks of the cycle
-#* 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.
+#* Security uplift nominations during RC week will be reviewed by security team and release owner for feasibility to include in m-r.
+#* Security uplift nominations to the ESR branch will be reviewed by security team and release owner.