Release Management/Aurora Landing Process
Goal: Aurora is a channel between the nightly builds from mozilla-central and beta versions from mozilla-beta; as such its status is roughly "experimental". This page describes the various steps done by the release team during this cycle.
The current aurora will be Firefox 54.
The Aurora repo: https://hg.mozilla.org/releases/mozilla-aurora/
More info about the Aurora:
What should land on mozilla-aurora: See the Uplift rules
The associated flags:
approval-mozilla-aurora: ?, +, -
tracking-firefox54: ?, +, -
status-firefox54: ?, unaffected, wontfix, affected, checkin-pending, fixed, verified
Aurora Triage Queries
aurora
Please note that the tracking flags follow the release, meaning that once aurora is merged to beta, the tracking and status flags remain during the beta cycle.
Aurora Timeline and Activities
A few days before the merge day
- Write the release notes
- Ask for review of the release notes
- Make sure we have the copy for any whatsnew pages in the localization team's hands. Talk with wbowden, jdouglas, :Pike and :flod. Make sure there's a bug for whatsnew work, and track it.
Aurora update day
- Once QA has signed off the release (usually later in release week, on Friday) send the aurora update email to release-drivers
- Mark release notes as public
- In product-details, update firefoxDetails.class.php and mobileDetails.class.php (do not touch the history files)
Weekly
Review aurora queries
- for potential uplifts
- to review uplift requests
- for potential tracking request
- to follow up on approved uplifts that have not landed
- Keep track of the tracked bugs without assigned developers
Week 4
- Keep track of the tracked bugs without fix
Merge day
TODO
Sample E-mails
Enable aurora updates
Subject: Please enable Aurora updates
Now that we've received QA sign off on both Desktop and Mobile FF{{AURORA_VERSION}}.0a2 builds, please go ahead with enabling updates.
<name>
Firefox Release Manager