Confirm
2,814
edits
Changes
m
→ESR Timeline and Activities: added a note about sec bugs.
* for potential ESR uplifts
* to review uplift requests
* to follow up on approved uplifts that have not landed* Note: if you don't have [https://www.mozilla.org/en-US/about/governance/policies/security-group/bugs/ security bug access], please ask another release manager to check the sec-critical bugs to nominate them and cc you.
=== Week 4 ===
Tue: Send [[Release_Management/ESR_Landing_Process#Smoke_Test_Request|smoke test e-mail]] to enterprise list
</pre>
[[category:Release_Management|E]]
= Branching Logistics =
When we have the overlapping ESR (and the first build of a major version number for the ESR.next - 10, 17, 24, 31, etc) we do build a separate build with its own branding from the newly minted branch. See https://wiki.mozilla.org/Releases/Firefox_24.0.esr/BuildNotes for how to kick off the builds and http://hg.mozilla.org/releases/mozilla-esr31/rev/e91c79c4c04b for an example of the custom configs needed for that first build's partials that has to land before kicking off the build in ship-it.
