Firefox Team Release Process

How the following will look

There will be 4 columns for the following below:

1. Person of Contact (Who owns this task)
2. Expected time (how long it takes to estimated complete the process)
3. Actual Time (how long it actually took to complete)
4. Notes (includes paths to builds, results, bonsai query. It can include a Mail button that generates the status update to release-drivers alias)

Step by Step process

1. Code Freeze (announced by Dev)

2. Dev Signs off / hands off to Build Team

3. Build Team team begins building

• tagging
• Generate Source Tarball
• Generate Binaries for:
  • Mac
  • Linux
  • Windows (signed)
  • all platforms including l10n

4. Build Team hands off builds in completion order to QA Team:

• • Mac
  • Linux
  • Windows (signed)
  • all platforms including l10n

5. QA Team runs tests:

• Smoketests on all Platforms (handed in order of release)
• BFTs on all platforms
• Focused Testing
• L10n

6. Build team generated mars for updates

• Build Team publishes updates to betatest Channel
• QA tests updates on betatest channel

7. Build Team publishes updates to Beta Channel

• QA tests updates on beta channel
• Monitor public forums for beta testing feedback

8. "Go/Nogo" decision

• Signoff from Dev, QA, Build, IT, and Release Notes

9. Push out bits to the mirrors

10. Build publishes updates to releasetest channel

• QA tests updates on releasetest channel

11. Build Team publishes updates to release channel (live bits)

• QA tests updates on release channel

12. Announce to the world

• all.html is updated on live site
• Download page is updated on live site
• Release notes is published on live site
• Someone announces release to media