Firefox GA Release

See also

Disclaimer

Name	Description
Determine L10N changesets	Finalize and ship L10N
Initiate release	Start release via Ship-It! application
Build everything	Automation will build installers and updaters for all locales and all platforms. (Progress emails are sent, some of which enable QE to begin phases of testing. That level of detail is not shown in this diagram.)
functional & updater testing	initiated by automated email QE tests all produced artifacts, obtained via internal links.
Decide build will be a GO	Manual email from QE initiates Decide if this build is acceptable, or another is needed. Restart process for new build.
push installers to mirrors	Manual email from RelMgmt initiates Push Installers and updaters to Mirrors
verify updater links	initiated by automated email QE verifies installers are properly accessible, and updates are served via normal mechanisms.
Set throttle % & go for live updaters	Manual email from QE initiates Decide when the release should become visible to end users.
configure update %	Manual email from RelMgmt initiates Apply throttling
push updaters live	Manual email from RelMgmt and completion of update_verify initiates Deploy the updater artifacts to the production release site. End users will be offered updates at this point.
verify throttling and live updaters	Manual email from RelEng initiates QE verifies that update throttling is at the correct level, and end users will be served accordingly.
make fully visible	Manual email from QE initiates Do final clean up of the release, including making visible on the FTP servers.
Party!	Everything completed for this release.

Note

All “RelEng” steps in the “Description” column above are taken from our checklist for Firefox Releases.