297
edits
Release Management/Release Process: Difference between revisions
Release Management/Release Process (view source)
Revision as of 12:33, 3 December 2019
, 3 December 2019update for shorter release cycles
m (→Android specificities: fixed a broken link) |
(update for shorter release cycles) |
||
| Line 25: | Line 25: | ||
== Release timeline == | == Release timeline == | ||
Firefox is released at intervals of | Firefox is released at intervals of four to five weeks (not counting urgent patch updates), meaning that every four to five weeks there | ||
will be a new version of Firefox Release. | will be a new version of Firefox Release. | ||
=== From mozilla-central to mozilla-release === | === From mozilla-central to mozilla-release === | ||
* Firefox Nightly is released every 12 hours with all the changes landed on mozilla-central. | * Firefox Nightly is released every 12 hours with all the changes landed on mozilla-central. | ||
* Every | * Every 4 to 5 weeks, we merge the code from mozilla-central to our mozilla-beta branch. The mozilla-beta branch should now only get patches aimed at stabilizing the release. Any patch on mozilla-central that we want backported to our mozilla-beta branch should follow the [[Release_Management/Uplift_rules|approval rules for uplifts]]. | ||
* | * Firefox Beta is released three times a week for Desktop, leaving us with 9 to 12 betas every cycle unless we have chemspills leading to additional betas. Firefox Beta 1 and 2 are shipped to a subset of our Beta population. The full Beta population gets updated starting with beta 3 only. | ||
* At the end of the Beta cycle, a final build is validated by our QA and tagged for release into the mozilla-release branch. | * At the end of the Beta cycle, a final build is validated by our QA and tagged for release into the mozilla-release branch. | ||
=== Android specificities === | === Android specificities === | ||
* Firefox Nightly is released every 24 hours | * Firefox Nightly is released every 24 hours | ||
* | * Firefox Beta is released once a week for Android, leaving us with 3 to 4 betas every cycle. | ||
Release day activities/checklist can be found on the [[Release_Management/Release_Day|Release Day wiki page]]. | Release day activities/checklist can be found on the [[Release_Management/Release_Day|Release Day wiki page]]. | ||
Our release schedule is meant to be flexible and we may occasionally modify the length of a cycle to be shorter or longer than the | Our release schedule is meant to be flexible and we may occasionally modify the length of a cycle to be shorter or longer than the 4-5 week cycle mentioned. Check the [[Release_Management/Calendar|Release Calendar]] to stay updated with the upcoming branch dates. | ||
=== Nightly soft code freeze === | === Nightly soft code freeze === | ||
The last | The last few days of the nightly cycle, before merge day (when mozilla-central is merged into the mozilla-beta repository and a new release cycle starts), is a nightly soft code freeze, meaning that developers should not land on mozilla-central code that is deemed risky for the stability and general quality of Firefox and that features that are controlled by a pref and were not activated during the nightly cycle should not be activated during this week. | ||
If you land code that introduces new crashers or lower the overall quality of Firefox during that period, we will back it out instead of waiting for a follow-up fix. | |||
== All about Flags == | == All about Flags == | ||
| Line 172: | Line 170: | ||
* '''Mailing Lists for any release-related issue''' | * '''Mailing Lists for any release-related issue''' | ||
** release-mgmt@mozilla.com | ** release-mgmt@mozilla.com | ||
** release-drivers@mozilla. | ** release-drivers@mozilla.org | ||
** enterprise@mozilla.org(enterprise related issues) | ** enterprise@mozilla.org(enterprise related issues) | ||
* '''Google groups''' | * '''Google groups''' | ||