Confirmed users
2,816
edits
Release Management/ESR Landing Process: Difference between revisions
Release Management/ESR Landing Process (view source)
Revision as of 16:15, 10 September 2015
, 10 September 2015→What should land on mozilla-esr{{ESR_CURRENT}}/mozilla-esr{{ESR_NEXT}}: note on what to uplift
m (→ESR{{ESR_CURRENT}}: added new smaller query to find anything sec-high or critical that we've missed) |
m (→What should land on mozilla-esr{{ESR_CURRENT}}/mozilla-esr{{ESR_NEXT}}: note on what to uplift) |
||
| Line 15: | Line 15: | ||
===What should land on mozilla-esr{{ESR_CURRENT}}/mozilla-esr{{ESR_NEXT}}=== | ===What should land on mozilla-esr{{ESR_CURRENT}}/mozilla-esr{{ESR_NEXT}}=== | ||
Security and some major stability fixes when they're landed/merged onto mozilla-beta, or fixes for regressions specific to the ESR. Exception: If patches only make changes to tests, test harnesses or anything else that does not affect the shipped builds, they may land with self approval (use a=testonly, a=npotb etc). | Security and some major stability fixes when they're landed/merged onto mozilla-beta, or fixes for regressions specific to the ESR. In the first few cycles of ESR we may be more flexible on these criteria. As the versions progress we should limit this to the most critical security fixes. | ||
Exception: If patches only make changes to tests, test harnesses or anything else that does not affect the shipped builds, they may land with self approval (use a=testonly, a=npotb etc). | |||
=== The associated flags=== | === The associated flags=== | ||