Firefox/Input/Release Checklist

Team

• Product lead: aakashd
• Dev lead: fwenzel/davedash
• QA lead: stephend
• IT lead: push bug assignee

Get Ready

1. Decision on release date and features - Product/Dev Lead
   • Update Firefox/Input page - Product lead
   • Email input@mo with proposed schedule and version number - Product lead
2. Triage of blocking/approval requests as needed - Product/Dev Lead
3. Update staging data from prod if necessary.
   • Until this is automated, make sure to change both instances of input.moz.com under Django admin -> Sites back to input.stage.moz.com. Otherwise the mobile site won't be served.

Get Set

1. Declare a string freeze - Dev lead
   • Notify localizers.
2. File push bug in mozilla.org/Server Operations - Web Content Push - Product lead
   • Offer a date and time to IT - Product lead
3. Enact a code freeze - Dev lead
   • Email input@mo with notification
4. Staging verification - QA Lead
   • QA performs release testing
   • When signed off, email input@mo with notification
   • Update push bug with QA sign off
5. Create release notes blog post - Product Lead
   • Confirm release notes with Dev lead, QA lead, others as appropriate
6. Determine a Go or no Go - Product lead
   • If No Go, email input@mo with a formal "stop" notification and a second "go" notification when the process is started again
   • If Go, mention on push bug and input@mo 8 hours ahead of time.
     • Make sure an IT lead is assigned to the bug and there is a push time.
     • Tag the branch for release with the appropriate version - Dev lead

Go!

1. Push to production at assigned time - IT lead
   • Update sphinx (via Puppet)
   • Run /root/bin/input_update.sh
   • Update update_product_details script
   • Run Crons mentioned by Dev lead
   • Clear out the cache
2. QA verifies production changes - QA Lead
3. Send out the blogpost - Product lead