QA/Desktop Firefox/Walkthroughs/Release Coordination

Nightly

Firefox starts on mozilla-central, this is where the initial code is landed to deliver new features to users. Every six weeks the current Nightly version is uplifted to the Aurora branch then Nightly becomes the next Firefox version. This "uplift" always happens on a Monday, except when people are unavailable due to statutory holidays.

For reference, here's a typical Firefox Nightly test plan.

Consult our walkthroughs for more information on QA processes.

Timeline

The following describes the general timeline for the entire six week life-cycle of a typical Nightly.

• Day 1:
  • Release Management updates the mozilla-central branch to the new version
  • QA Lead creates initial test plan to track important bugs and new features
  • QA Lead signs off initial Nightly builds
• Interim:
  • Developers land changes, fixes, and new features
  • QA tests these changes, fixes, and features as they land
  • QA Lead ensures important features and bugs are escalated and assigned
• Day 42:
  • QA signs off features and builds as ready for Aurora by prior to migration
  • Release Management closes the tree and merges mozilla-central to mozilla-aurora

Priorities

• Ensuring topcrash bugs are being investigated
• Ensuring iteration developed bugs are owned and signed off
• Ensuring new features are owned and on track for sign-off
• Ensuring fixed bugs are being verified
• Ensuring reported bugs are being triaged