Changes

Jump to: navigation, search

Release Management/ESR Landing Process

159 bytes added, 16:15, 10 September 2015
m
What should land on mozilla-esr{{ESR_CURRENT}}/mozilla-esr{{ESR_NEXT}}: note on what to uplift
===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. 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===
Confirm
2,814
edits

Navigation menu