MozillaWiki

Release Management: Difference between revisions

(minor fixes)
No edit summary
 
(5 intermediate revisions by 2 users not shown)
Line 23: Line 23:


;Matrix
;Matrix
* [https://chat.mozilla.org/#/room/#release-discussions:mozilla.org #release-discussions] - Firefox Desktop and Android release drivers. Good way to contact release managers, ask questions, escalate issues.
* [https://chat.mozilla.org/#/room/#release-drivers:mozilla.org #release-discussions] - Firefox Desktop and Android release drivers. Good way to contact release managers, ask questions, escalate issues.


;Twitter
;Twitter
Line 63: Line 63:
* [[Release_Management/Release_Process_Checklist_Documentation|Release Process Checklist Documentation]] - for our fabulous new checklists (Find those linked from the pages for an individual release, for example for [[Releases/Firefox_66|Firefox 66]]).
* [[Release_Management/Release_Process_Checklist_Documentation|Release Process Checklist Documentation]] - for our fabulous new checklists (Find those linked from the pages for an individual release, for example for [[Releases/Firefox_66|Firefox 66]]).
* [https://wiki.mozilla.org/Release_Management/ESR_Landing_Process ESR Triage]
* [https://wiki.mozilla.org/Release_Management/ESR_Landing_Process ESR Triage]
* [[Release_Management/Mobile_Publishing_Documentation|Publishing to Mobile stores]]
* [[Release Management/Process coordination for handling off-train releases|Process coordination for handling off-train releases]]
* Releng release flow for [http://moz-releng-docs.readthedocs.org/en/latest/release_workflows/fx_beta_release.html Beta] and [http://moz-releng-docs.readthedocs.org/en/latest/release_workflows/fx_ga_release.html Release]
* Releng release flow for [http://moz-releng-docs.readthedocs.org/en/latest/release_workflows/fx_beta_release.html Beta] and [http://moz-releng-docs.readthedocs.org/en/latest/release_workflows/fx_ga_release.html Release]
* [https://drive.google.com/open?id=1x27I7hAmWDWiqk3o3YC3fklhE3N59bdgHCQHF5p_lkU GoFaster release and relnote process] and other [https://docs.google.com/document/d/1_Xga8Mkb3IBZiiMlZiIfLuEtrjnFA1UZkiD0S7nKsjA/ Off-train releases]
* [https://drive.google.com/open?id=1x27I7hAmWDWiqk3o3YC3fklhE3N59bdgHCQHF5p_lkU GoFaster release and relnote process] and other [https://docs.google.com/document/d/1_Xga8Mkb3IBZiiMlZiIfLuEtrjnFA1UZkiD0S7nKsjA/ Off-train releases]
Line 71: Line 69:
;Dashboards
;Dashboards
* [https://mozilla.github.io/delivery-dashboard/ Delivery Dashboard]
* [https://mozilla.github.io/delivery-dashboard/ Delivery Dashboard]
* [[Release_Management/Review_Fixes_Worth_Uplifting|Review important bug fixes landed in Nightly for uplift to Beta, ESR]]
* [https://bugdash.moz.tools/#tab.beta Beta channel Blockers and Regressions]
* [http://mozilla.github.io/releasehealth/?channel=release Release channel Blockers and Regressions]
* [https://bugdash.moz.tools/#tab.reo Nightly, Beta, and Release Regressions Triage]
* [http://mozilla.github.io/releasehealth/?channel=beta Beta channel Blockers and Regressions]
* [https://mozilla.cloud.looker.com/dashboards/918 Stability dashboard]
* [http://mozilla.github.io/releasehealth/?channel=nightly Nightly channel Blockers and Regressions]
* [https://sql.telemetry.mozilla.org/dashboard/release-management-dashboard Stability dashboard]
* [https://mozilla.github.io/stab-crashes Stability deep-dive scripts]
* [https://whattrainisitnow.com/ Firefox Trains & Release Insights] - Firefox Trains dashboard, overview of past and future releases (milestones, key numbers)  
* [https://whattrainisitnow.com/ Firefox Trains & Release Insights] - Firefox Trains dashboard, overview of past and future releases (milestones, key numbers)  
* [https://pascalc.net/rm_queries/  Popular Queries] - A collection of Bugzilla and Socorro queries used daily by release managers
* [https://pascalc.net/rm_queries/  Popular Queries] - A collection of Bugzilla and Socorro queries used daily by release managers
Line 82: Line 77:


;Release managers also help with ways we can update aspects of Firefox on the fly, including graphics driver and plugin blocklisting.
;Release managers also help with ways we can update aspects of Firefox on the fly, including graphics driver and plugin blocklisting.
* [[Blocklisting|Blocklisting]]
* [https://extensionworkshop.com/documentation/publish/add-ons-blocking-process/ Blocklisting]
* [[Firefox/Go_Faster/System_Add-ons/Process|System add-ons]] (also known as Go Faster add-ons)
* [[Firefox/Go_Faster/System_Add-ons/Process|System add-ons]] (also known as Go Faster add-ons)


Latest revision as of 18:35, 19 May 2026

All-firefox-logos.png

Quick Links

About Release Management

The Release Management team keeps the release process on track for upcoming releases. We focus on release quality, security, and stability. As release managers follow specific features and individual bugs, we work with developers, engineering managers, product managers, UI/UX teams, QE, and release engineering, doing whatever it takes to coordinate the many details in the creation of a new version of Firefox. We aim to get features & fixes landed in time for proper evaluation. Our goal is to ship the most stable & excellent product possible for Firefox Desktop & Mobile for our users.

Contribute

There are many ways to help the release management team. Help with tracked bugs, triage crashes, report regressions that affect Firefox on pre-releasechannels or hack on the tools our team develops and maintains.

Developers and anyone in the community can help by proposing bugs for tracking, using the tracking flags in bugzilla.mozilla.org.

Team info

Communication Channels

E-mail
  • Team distribution list: release-mgmt at mozilla dot com
Matrix
  • #release-discussions - Firefox Desktop and Android release drivers. Good way to contact release managers, ask questions, escalate issues.
Twitter
Blog
Slack

Meetings

We host and are a part of number of meetings. You can't miss us at channel meetings, where we discuss and try to resolve any release related issues. Anyone working to get a new feature or complicated fix into Firefox may want to join the channel meeting to discuss the process with the entire team of release managers. User advocacy, QE and stability, and release engineering team members also often join the channel meetings.

Calendar Updating

To add the basic release calendar to your Google calendar if you have a mozilla.com email:

  • Go to your calendar
  • In the upper right, click on the Gear icon and click on Settings in the pop up menu
  • In the Settings page, click on Add Calendar in the left menu
  • Click on Browse ressources in the sub-menu
  • Click on Public in the main pane
  • Click on the checkbox next to Public - Firefox Merge/Release Schedule
  • You can also add "Public- Releases Scheduling" here for a more detailed view.

Direct calendar link: Firefox Merge/Release Schedule calendar

When the release schedule is adjusted for any reason, we need to ensure that our calendar is updated to reflect this. If the calendar itself is updated, there is a link to it on this page (at the top) as well as on the release calendar.

Documentation

Each version of Firefox is followed by a release manager who owns it from start to release. This way, Nightly, Beta, ESR, and Release channels have someone dedicated to getting all the pieces put together correctly.


Dashboards
Release managers also help with ways we can update aspects of Firefox on the fly, including graphics driver and plugin blocklisting.
Here are some guidelines for developers, product managers, and our team as well.


Tools
Retrieved from "https://wiki.mozilla.org/index.php?title=Release_Management&oldid=1257420"