Confirm
2,814
edits
Changes
m
this time formatted correctly
When the release schedule is adjusted for any reason, we need to ensure that [https://calendar.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ our calendar] is updated to reflect this. If the calendar itself is updated, there is a link to it on this page (at the top) as well as on the [[Release_Management/Calendar|release calendar]].
==DocumentationsDocumentation==
Each version of Firefox is followed by a release manager who owns it from start to release. This way, Nightly, Beta, ESR, and Release channels have someone dedicated to getting all the pieces put together correctly.
* [[Release_Management/Release_owners|Release Owners]]
* [[Release_Management/Release_Process_Checklist_Documentation |Release Process Checklist Documentation]] - for our fabulous new checklists (Find those linked from the pages for an individual release, for example for [[Releases/Firefox_66 |Firefox 66]]).
* [https://wiki.mozilla.org/Release_Management/ESR_Landing_Process ESR Triage]
* [[Release_Management/Mobile_Publishing_Documentation|Publishing to Mobile stores]]
* [https://mozilla.github.io/stab-crashes Stability deep-dive scripts]
* [https://www.flickr.com/photos/lizhenry/24368249885 Dashboard the Cat] - she likes to eat headphones
;Release managers also help with ways we can update aspects of Firefox on the fly, including graphics driver and plugin blocklisting.
