Changes

Jump to: navigation, search

Release Management/Release Process

19 bytes removed, 12:33, 10 August 2020
some updates
* [https://play.google.com/store/apps/details?id=org.mozilla.firefox Firefox for Android]
* [https://play.google.com/store/apps/details?id=org.mozilla.firefox_beta Firefox Beta for Android]
* [https://play.google.com/store/apps/details?id=org.mozilla.fennec_aurora fenix Firefox Nightly for Android]
== Release timeline ==
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.
=== From mozilla-central to mozilla-release ===
* Firefox Nightly contains all the changes landed on mozilla-central. Regular Nightly releases occur about every 12 hours, with additional releases generated when a Nightly release has a major problem.
* 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.
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 lowers the overall quality of Firefox during that period, we will back it out instead of waiting for a follow-up fix.
== All about Flags ==
[[File:Status.png|400px|right]]
=== tracking-firefoxXX ===
A flag which show shows whether a bug is being investigated for possible resolution in the Firefox XX release. Bugs marked tracking-Firefox XX are bugs that must be resolved one way or another before a particular release ships. [[Firefox/Drivers|Release drivers]] will track and shepherd the bug until it is determined the bug no longer impacts the release.
{| class="wikitable"
'''Note:''' Bugs denied for ''tracking-Firefox XX'' are still important. It merely means based on the information we have now,we do not feel the bug would prevent us from shipping a release. If new information comes to light, you need help getting more data before you can make the case for us to track, or you disagree with our assessment feel free to renominate again with additional justification.
3) Once you nominated a patch with '''approval-mozilla-beta/release: ?''' we will evaluate the information given in the attachment request we may either approve/deny/request more information. Once you get an approval , i.e '''approval-mozilla-beta/release: +''', please go ahead with landing sheriffs or release managers will land it on the corresponding branch and mark '''status-Firefox XX''' flag to ''fixed'', making sure [https://treeherder.mozilla.org/ Treeherder] is green.
** release-mgmt@mozilla.com
** release-drivers@mozilla.org
** enterprise@mozilla.org(enterprise related issues)
* '''Google groups'''
** mozilla.dev.platform
287
edits

Navigation menu