Release Management: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (centering the quick links box)
m (Link update)
 
(50 intermediate revisions by 11 users not shown)
Line 1: Line 1:
__NOTOC__
__NOEDITSECTION__
__NOEDITSECTION__
<div style="-moz-border-radius: 10px;width:38%;background-color:#FFF;display:block;margin:1.5%;border: 1px solid #00539F;text-align:center;padding:2.5%;padding-top:0px;margin-left:25%">[[File:FF-wordmark-logo.png|250px|link=Release_Management/Firefox_Browser]]
[[File:All-firefox-logos.png|500px|center]]
===Quick Links===
=Quick Links=
* [[RapidRelease/Calendar | Release Calendar ]]
* [https://whattrainisitnow.com/calendar/ Release Calendar overview ]
* [[RapidRelease | Release Process]]
* The [[Release_Management/Release_Process | Release Process]] explained
* [[Releases | Current and Past Releases]]
* [[Releases | Current and Past Releases]]
* [https://www.google.com/calendar/embed?src=mozilla.com_2d37383433353432352d3939%40resource.calendar.google.com Public Firefox Merge/Release Scheduling Calendar]
* [https://www.google.com/calendar/embed?src=mozilla.com_dbq84anr9i8tcnmhabatstv5co%40group.calendar.google.com Release Scheduling Calendar] (more detailed)
* [[Release_Management/Onboarding | Onboarding]]
</div>


<div style="clear:both">
=About Release Management=
</div>
The Release Management team keeps the [[Release_Management/Release_Process | 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 =


=<center>About Release Management Team</center>=
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.


'''The Release Management Team is tasked with ensuring the release process is on track while ensuring quality releases of our products for users.'''
Developers and anyone in the community can help by proposing bugs for tracking, using the tracking flags in bugzilla.mozilla.org.


= Team Members =
= Team info =
[[Release_Management/Team_members]]
* [[Release_Management/Team_members]] List of release managers, past and present


==Communication Channels==
==Communication Channels==
;E-mail
;E-mail
* Team distribution list: release-mgmt at mozilla dot com
* Team distribution list: release-mgmt at mozilla dot com
;IRC
 
* [irc://irc.mozilla.org/%23relman #relman] - Release Management specific channel
;Matrix
* [irc://irc.mozilla.org/%23release-drivers #release-drivers] - Firefox Desktop and Android release drivers
* [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.
 
;Twitter
;Twitter
* [https://twitter.com/MozillaReleases @MozillaReleases]
* [https://twitter.com/MozillaReleases @MozillaReleases] Release Management team communication channel
* [https://twitter.com/FirefoxNightly @FirefoxNightly] Firefox Nightly communication and feedback channel
* [https://twitter.com/FirefoxBeta @FirefoxBeta] Firefox Beta communication and feedback channel
 
;Blog
* [http://release.mozilla.org/ Release Management Blog]
 
;Slack
* [https://mozilla.slack.com/messages/release-coordination/ #release-coordination]


==Meetings==
==Meetings==


We host and are a part of number of meetings but you can't miss us at Channel Meetings,Postmortems,Release sign-offs where we discuss and try to resolve any release related issues.
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.
* Channel Meeting  
 
**This meeting takes place twice a week on Tuesday at 10 AM PT and Thursday at 2 PM PT in Release Coordination Vidyo Room
* Channel Meeting
**[https://wiki.mozilla.org/Firefox/Channels/Meetings Channel Meeting Wiki Archive]
** This meeting takes place twice a week on Tuesdays 10am Pacific time and Thursdays at 8am Pacific time
* Release Sign-offs
** [https://wiki.mozilla.org/Firefox/Channels/Meetings Channel Meeting Wiki Archive]
**This meeting happens a week before we are ready to ship at the Thursday Channel Meeting to address any outstanding concerns around the release
**[https://wiki.mozilla.org/Releases/Firefox_{{CURRENT_VERSION}}/Final_Signoffs Release sign-off meeting ]
* Release Post Mortem
* Release Post Mortem
**This meetings happens at the Tuesday Channel Meeting two weeks after a release
** This meetings happens at the Tuesday Channel Meeting two weeks after a release
** [https://wiki.mozilla.org/Releases/Post-mortems/Firefox_{{CURRENT_VERSION}}.0 Postmortem Schedule & Agenda]
** [https://wiki.mozilla.org/Releases/Post-mortems/Firefox_{{Version/Gecko/release/current}}.0 Postmortem Schedule & Agenda]


==Quarterly Goals==
==Calendar Updating==
To add the basic release calendar to your Google calendar if you have a mozilla.com email:
* Go to your [https://calendar.google.com/ 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: [https://calendar.google.com/calendar?cid=bW96aWxsYS5jb21fMmQzNzM4MzQzMzM1MzQzMjM1MmQzOTM5QHJlc291cmNlLmNhbGVuZGFyLmdvb2dsZS5jb20 Firefox Merge/Release Schedule calendar ]


[[Release_Management/Quarterly_Goals]]
When the release schedule is adjusted for any reason, we need to ensure that [https://calendar.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ 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_Management/Calendar|release calendar]].


==Release Owners==
==Documentation==
[[Release_Management/Release_owners]]
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.
* [[Release_Management/Release_owners|Release Owners]]
* [[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]
* [[Release_Management/Mobile_Publishing_Documentation|Publishing to Mobile stores]]
* [[Release Management/Release Days|Release Days]] Merge and release day processes
* [[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]
* [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]


==Dashboards==


==Calendar Updating==
;Dashboards
When the release schedule is adjusted for any reason, we need to ensure that https://www.google.com/calendar/embed?src=mozilla.com_u92lbs8k7tj4a9j4qc231ov3co%40group.calendar.google.com 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 [[RapidRelease/Calendar]]
* [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]]
* [http://mozilla.github.io/releasehealth/?channel=release Release channel Blockers and Regressions]
* [http://mozilla.github.io/releasehealth/?channel=beta Beta channel Blockers and Regressions]
* [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://pascalc.net/rm_queries/  Popular Queries] - A collection of Bugzilla and Socorro queries used daily by release managers
* [https://phabricator.services.mozilla.com/dashboard/view/108/ Phabricator Uplift Request Dashboard] - Pending uplift requests in Phabricator.


==Team Resources==
;Release managers also help with ways we can update aspects of Firefox on the fly, including graphics driver and plugin blocklisting.
* [[Firefox/Hotfix | Hotfix process documentation]]
* [https://wiki.mozilla.org/User:Akeybl/Release_Dash Firefox Triage Dashboard]
* [https://wiki.mozilla.org/RapidRelease/Calendar Rapid Release Calendar]
* [https://wiki.mozilla.org/B2G/Triage B2G Triage Page]
* [https://wiki.mozilla.org/Release_Management/ESR_Landing_Process ESR Triage]
* [https://wiki.mozilla.org/Release_Management/B2G_Landing#Versions_and_Scheduling B2G Landing]
* [https://intranet.mozilla.org/Program_Management/Firefox_OS/Localization FXOS Localizations] (auth required)
* [http://ship-it.mozilla.org/ Ship-it UI] - Need to be on MPT VPN
* [https://v.mozilla.com/flex.html?roomdirect.html&key=EXysadF68Dac Release Coordination Vidyo Link]
* [[Firefox/Hotfix|Shipping a hotfix]]
* [[Blocklisting|Blocklisting]]
* [[Blocklisting|Blocklisting]]
* [[Release_Management/Mobile_Publishing_Documentation|Publishing to Mobile stores]]
* [[Firefox/Go_Faster/System_Add-ons/Process|System add-ons]] (also known as Go Faster add-ons)
* [[Release_Management/aurora_Landing_Process|Aurora Landing Process]]
 
* 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]
;Here are some guidelines for developers, product managers, and our team as well.
* [[Release_Management/Uplift_rules|Uplift rules]]
* [[Release_Management/Requesting_an_Uplift|How to request an uplift]]
* [[Release_Management/Approving_uplift_requests|How to approve and land uplifts]]
* [[Release_Management/Tracking_rules|Tracking rules]]
* [[Release_Management/Relnotes_rules|Release notes rules]]
* [[Release_Management/Glossary|Glossary of terms used by Release Management]]
 
 
;Tools
* [https://shipit.mozilla-releng.net/ Ship-it UI] - [https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=30769829 Mozilla VPN]
* [https://balrog.services.mozilla.com/ Balrog admin UI] - requires VPN
* [[Release_Management/Product_details|Product-Details]], a public JSON API about Firefox and Thunderbird releases
* [[Release_Management/Onboarding|Onboarding]]
* [[Release_Management/autonag|Autonag - the nagging tool]]
 
 
[[Category:Release_Management]]
[[Category:Release_Management]]

Latest revision as of 12:36, 29 March 2023

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://dev.wikimo.nonprod.webservices.mozgcp.net/index.php?title=Release_Management&oldid=1245958"