Release Management/Release Process: Difference between revisions

* '''Firefox Release/[https://hg.mozilla.org/releases/mozilla-release mozilla-release]''' — The official release of Firefox.

* '''Firefox Beta/[https://hg.mozilla.org/releases/mozilla-beta mozilla-beta]''' — Testing the next version of Firefox before it becomes the official release. Firefox Beta channel is also built from the Beta branch.

* '''Firefox Nightly/[https://hg.mozilla.org/mozilla-central mozilla-central]''' — Nightly releases that contains experimental features (covered regularly on Twitter from [https://twitter.com/FirefoxNightly @FirefoxNightly]).

* '''Firefox ESR/[https://hg.mozilla.org/releases/mozilla-esr{{ESR_CURRENT}}/ mozilla-esr{{ESR_CURRENT}}]''' — Official Desktop releases for Organizations. Check the [https://wiki.mozilla.org/Release_Management/ESR_Landing_Process wiki] for detailed information.

See the [[Tree_Rules|Tree Rules]] before pushing patch into any repository.

[[File:Maintrepositories.png|center]]

== Download Links for Firefox for Desktop==

Get the latest version of Firefox for Windows, macOS or Linux across all channels and check the Release notes for new features, enhancements or changes.

* [https://www.mozilla.org/firefox/ Firefox Release]

* [https://www.mozilla.org/firefox/beta/ Firefox Beta]

* [https://www.mozilla.org/firefox/developer/ Firefox Dev Edition]

* [https://www.mozilla.org/firefox/nightly/ Firefox Nightly]

* [https://www.mozilla.org/firefox/organizations/ Firefox ESR (Extended Support Release)]

== Download Links for Firefox for Android ==

You can get the latest release, beta and Nightly versions of Firefox for Android on the Google Play Store.

* [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.fenix Firefox Nightly for Android]

The standard release interval of Firefox is four weeks (not counting urgent patch updates), meaning that every four weeks there

will be a new version of Firefox Release. The release interval is sometimes lengthened due to holidays.

* 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 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]].

=== Android specificities ===

* 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]].

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.

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.

== All about Flags ==

See [https://wiki.mozilla.org/BMO/UserGuide#Tracking_Flags BMO documentation on Flags]

1) If you think a bug needs to be addressed in a release:

* Set the '''tracking-Firefox XX: ?''' nomination on a bug for with helpful justification and keeping these [https://blog.mozilla.org/channels/2011/06/01/more-details-about-how-to-use-the-tracking-firefox-bugzilla-flag/ guidelines] in mind

* Once the patch is ready set the approval flag appropriately depending on which branches are affected

2) Members of Release Management go through all the bugs nominated for tracking and if in agreement that this bug needs to be investigated in that release we will go ahead and set '''tracking-Firefox XX: +'''. Once we track a bug for a particular release we will make sure to follow-up on the progress or help with any road blockers till you have a patch nominated for approval.

'''Note:''' In the case that a tracked bug is resolved as a duplicate bug, it is best practice for the release management team to remove the tracking flag from the duplicate bug and add it to the active linked bug.  

* [[Release_Management/Tracking_rules|Tracking Rules]]

* [[Release_Management/Uplift_rules|Uplift Rules]]

* Type '''about:crashes''' in Firefox to get links to your crashes.

* You can obtain crash-data across any channel for all Firefox products by customizing the needed reports from [https://crash-stats.mozilla.com/products/Firefox the Socorro dashboard].

* If the information on the Socorro dashboard does not suffice for the crasher you are investigating and you need access to raw data, additional crash-dumps or other data related to the crash, you can file a Bug and forward the request to the Socorro team as a start to help you.

Following are the queries that Release management goes through almost day-day to make sure we are tracking the right blockers,getting them fixed and make sure these bugs get fixed (heard of nag emails yet:) ? )  for a particular Firefox release.

** [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;list_id=4754086;field0-1-0=cf_status_firefox{{BETA_VERSION}};field0-0-0=cf_tracking_firefox{{BETA_VERSION}};value0-3-0=unaffected;value0-6-0=verified%20disabled;value0-1-0=wontfix;field0-5-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;field0-3-0=cf_status_firefox{{BETA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;type0-3-0=notequals;field0-2-0=cf_status_firefox{{BETA_VERSION}};field0-4-0=cf_status_firefox{{BETA_VERSION}};type0-6-0=notequals Bugs] tracking Firefox Beta {{BETA_VERSION}}

** [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&keywords=topcrash%2C%20&keywords_type=allwords&list_id=6606248&v11=unaffected&j10=OR&o14=notequals&f13=OP&o2=equals&j16=OR&v5=wontfix&f12=CP&j4=OR&f14=cf_status_firefox{{BETA_VERSION}}&o17=notequals&o20=notequals&v2=%2B&f21=CP&f10=OP&f19=OP&f22=CP&f1=OP&f20=cf_status_firefox{{BETA_VERSION}}&j13=OR&f8=cf_status_firefox{{BETA_VERSION}}&f0=OP&j19=OR&o11=notequals&f18=CP&columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate&f15=CP&f9=CP&j7=OR&v20=verified%20disabled&f4=OP&query_format=advanced&j1=OR&v17=disabled&f3=CP&f2=cf_tracking_firefox{{BETA_VERSION}}&f11=cf_status_firefox{{BETA_VERSION}}&f5=cf_status_firefox{{BETA_VERSION}}&f17=cf_status_firefox{{BETA_VERSION}}&v8=fixed&v14=verified&f6=CP&f7=OP&o8=notequals&f16=OP Beta top-crashers]

* To ensure that these tracking Bugs get the needed attention and keeping in mind the deadlines in case you forget Release Management sends you friendly nag emails for these blocker email's to make sure these get the needed priority and attention as they are are considered potential blockers for release.

* If you are working on a tracked bug you may have seen emails with Subject similar to: '''''RelMan Attention Needed: Monday May 20 -- Daily Release Tracking Alert''''' for bugs that are actively not being worked on or if any of the bugs may have a '''needsinfo''' on you and is blocking progress.

* This has also been very helpful to avoid any communication gap between Release drivers and developers and help us be on the same page and setting the right expectation about a tracked bugs progress and resolution.

== Release notes for Desktop/Android ==

[[Release_Management/Relnotes_rules|Release Notes page]] describes the release notes process, the '''''relnote-firefox''''' tracking flag, styling guide and other relevant details.

Please check the [[Release_Management/Release_Notes_Process#What.27s_New.2FKnown_Issues_Section_Candidates Release Notes documentation]] for the process we currently have to construct release notes. Below are the links to all the existing release notes across all channels.

* '''Firefox Release'''

** [https://www.mozilla.org/firefox/releasenotes/ Desktop Release notes]

** [https://www.mozilla.org/firefox/android/notes/ Android Release notes]

 

 

== See [https://wiki.mozilla.org/Release_Management/Release_Process/FAQ FAQ] ==

* '''Matrix'''

** https://chat.mozilla.org/#/home and apps on various platforms.

** Useful rooms include #introduction:mozilla.org, #release-drivers:mozilla.org, and #developers::mozilla.org.

** [https://wiki.mozilla.org/Matrix More info on Matrix]

* '''Mailing Lists for any release-related issue'''

** release-drivers@mozilla.org

** enterprise@mozilla.org (enterprise related issues)

* '''Google groups'''

* '''Be part of the [[Firefox/Channels/Meetings|Channel Meetings]] if you are interested in day-day updates for desktop/mobile releases'''

 

[[Category:Release Management|Release Process]]

[[Category:Release Management:Processes|Release Process]]