Release Management: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(slack + utc + system addons)
(Update calendar instructions, update Beta checklist link)
Line 57: Line 57:


==Calendar Updating==
==Calendar Updating==
To add the basic release calendar to your Google calendar:
To add the basic release calendar to your Google calendar if you have a mozilla.com email:
* Go to your calendar
* Go to your [https://calendar.google.com/ calendar]
* In the lower left, choose Other Calendars
* In the upper right, click on the Gear icon and click on ''Settings'' in the pop up menu
* Choose "Interesting Calendars"
* In the ''Settings'' page, click on ''Add Calendar'' in the left menu
* Click the link "More" near the top of the page, by Holidays and Sports
* Click on ''Browse ressources'' in the sub-menu
* Click "Resources for mozilla.com"
* Click on ''Public'' in the main pane
* Click "Public"
* Click on the checkbox next to ''Public - Firefox Merge/Release Schedule''
* Choose "Firefox Merge/Release schedule"
* You can also add "Public- Releases Scheduling" here for a more detailed view.
* You can also add "Releases Scheduling" here for a more detailed view.
 
Direct calendar link: [https://calendar.google.com/calendar?cid=bW96aWxsYS5jb21fMmQzNzM4MzQzMzM1MzQzMjM1MmQzOTM5QHJlc291cmNlLmNhbGVuZGFyLmdvb2dsZS5jb20 Firefox Merge/Release Schedule calendar ]


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 [[RapidRelease/Calendar]]
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 [[RapidRelease/Calendar]]
Line 74: Line 75:
* [[Release_Management/Nightly|Nightly]] Tasks for relman during Nightly
* [[Release_Management/Nightly|Nightly]] Tasks for relman during Nightly
* [[Release_Management/Beta_Release_Checklist|Beta Release Checklist]]
* [[Release_Management/Beta_Release_Checklist|Beta Release Checklist]]
** Excel based checklist: [https://drive.google.com/open?id=1JjYHkyhSyACnu-UEL-a2PUbkHp1fcncDcdot-vs4d_E Beta 44 Release Checklist]
** Excel based checklist: [https://docs.google.com/spreadsheets/d/1hhYtmyLc0GEk_NaK45KjRvhyppw7s7YSpC9xudaQZgo/edit#gid=1158959417 Mid-beta and release checklist]
* [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/Mobile_Publishing_Documentation|Publishing to Mobile stores]]

Revision as of 17:06, 31 January 2018

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, 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.

The relman team maintains several tools. You can help by fixing bugs!

Team info

Communication Channels

E-mail
  • Team distribution list: release-mgmt at mozilla dot com
IRC
  • #release-drivers - Firefox Desktop and Android release drivers. Good way to contact release managers, ask questions, escalate issues.
Twitter
Blog
Visio
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 RapidRelease/Calendar

Team Resources

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