Changes

* '''Schedule push to esr at 100% (ship-it).'''Go-Live time is usually 6am PT on launch day, but this can be done ahead of time with a scheduled rule change in Balrog. Unlike non-ESR Firefox releases, ESR releases go out at 100% from day 1 rather than a staged rollout.* '''Make release notes live.'''There is a 15-20min lag between making the change in Nucleus and the live website picking up this change, so plan to do this 15-30min prior to go-live.* '''Signoff on scheduled rule change in Balrog.'''Assuming that the change is scheduled for 6am PT, this can be signed off ASAP to avoid unnecessary delays at go-live time.* '''Verify that new release is live on mozilla.org.'''Verify that download requests are pointing to the new version from the [https://www.mozilla.org/firefox/organizations/all/ download page]. This can probably be moved to the delivery dashboard.

* '''Update tests on esr.'''QA will send a sign-off email when this is completed.* '''Security advisories go live.'''This will be handled by the security team post-launch.* '''Send the announce email to enterprise list.'''After launch, an email like this one [https://mail.mozilla.org/private/enterprise/2018-December/000429.html] is sent to the enterprise mailing list.