Release Management: Difference between revisions
Jump to navigation
Jump to search
(+ various links) |
m (reorganizing the page a bit, rewriting some text. TODO: float text around that box thing in 2 columns! a TOC may be better anyway) |
||
| Line 1: | Line 1: | ||
__NOTOC__ | __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: | <div style="-moz-border-radius: 10px;width:38%;background-color:#FFF;display:inline-block;margin:1.5%;border: 1px solid #00539F;text-align:center;padding:2.5%;padding-top:0px;margin-left:3%">[[File:FF-wordmark-logo.png|250px|link=Release_Management/Firefox_Browser]] | ||
===Quick Links=== | ===Quick Links=== | ||
* [[RapidRelease/Calendar | Release Calendar ]] | * [[RapidRelease/Calendar | Release Calendar ]] | ||
* [[RapidRelease | Release Process]] | * The [[RapidRelease | 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 | * [https://www.google.com/calendar/embed?src=mozilla.com_2d37383433353432352d3939%40resource.calendar.google.com Firefox Merge/Release Calendar] | ||
* [https://www.google.com/calendar/embed?src=mozilla.com_dbq84anr9i8tcnmhabatstv5co%40group.calendar.google.com Release | * [https://www.google.com/calendar/embed?src=mozilla.com_dbq84anr9i8tcnmhabatstv5co%40group.calendar.google.com Release Calendar] (Details) | ||
</div> | </div> | ||
| Line 15: | Line 14: | ||
=About | =About Release Management= | ||
The Release Management Team | The Release Management Team keeps the release process on track while ensuring quality releases of our products and for users. We track work for upcoming releases, coordinating with any and all teams responsible for areas of release quality, security, and stability. As release managers track specific features and individual bugs, we work with developers, engineering managers, product managers, UI/UX teams, and QE, monitoring everything that goes into a new version of Firefox under development. We aim to get features & fixes (and sometimes backouts) landed in time for proper evaluation. Our goal is to ship the most stable & quality product possible for Firefox Desktop & Mobile. | ||
= Contribute = | = Contribute = | ||
| Line 23: | Line 22: | ||
There are many ways to help the release management team and be part of it. | There are many ways to help the release management team and be part of it. | ||
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! | |||
* Our [https://github.com/mozilla/relman-auto-nag automatic nag tool] to send email to Firefox developers about their bugs | |||
* | |||
* [https://bugzilla.mozilla.org/buglist.cgi?list_id=12453401&resolution=---&classification=Other&query_format=advanced&component=Ship%20It&product=Release%20Engineering ship-it] - interface to start builds of Firefox, Firefox for Android and Thunderbird | * [https://bugzilla.mozilla.org/buglist.cgi?list_id=12453401&resolution=---&classification=Other&query_format=advanced&component=Ship%20It&product=Release%20Engineering ship-it] - interface to start builds of Firefox, Firefox for Android and Thunderbird | ||
* | * Google Play scripts to [https://hg.mozilla.org/build/mozharness/file/tip/scripts/push_apk.py upload APK] and [https://hg.mozilla.org/build/mozharness/file/tip/scripts/update_apk_description.py manage translations] | ||
= Team | = Team info = | ||
[[Release_Management/Team_members]] | * [[Release_Management/Team_members]] List of release managers, past and present | ||
* [[Release_Management/Quarterly_Goals]] for the relman team | |||
==Communication Channels== | ==Communication Channels== | ||
| Line 44: | Line 41: | ||
;Twitter | ;Twitter | ||
* [https://twitter.com/MozillaReleases @MozillaReleases] | * [https://twitter.com/MozillaReleases @MozillaReleases] | ||
* [https://v.mozilla.com/flex.html?roomdirect.html&key=EXysadF68Dac Release Coordination Vidyo Link] | |||
==Meetings== | ==Meetings== | ||
| Line 57: | Line 55: | ||
**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_{{Version/Gecko/release/current}}.0 Postmortem Schedule & Agenda] | ** [https://wiki.mozilla.org/Releases/Post-mortems/Firefox_{{Version/Gecko/release/current}}.0 Postmortem Schedule & Agenda] | ||
==Calendar Updating== | ==Calendar Updating== | ||
| Line 71: | Line 60: | ||
==Team Resources== | ==Team Resources== | ||
Each version of Firefox is follwed by a release manager who owns it from start to release (and beyond). This way, Nightly, Aurora, Beta, ESR, and Release channels have someone dedicated to getting all the pieces put together correctly. | |||
* [[Release_Management/Release_owners]] | |||
* [[Release_Management/Nightly|Nightly]] Tasks for relman during Nightly | |||
* [[Release_Management/Aurora_Landing_Process|Aurora Landing Process]] What we do during the Aurora cycle | |||
* [[Release_Management/Beta_Release_Checklist|Beta Release Checklist]] | |||
* [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 | |||
* 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] | |||
;Release managers also help with ways we can update aspects of Firefox on the fly, including add-on hotfixes, and graphics driver and plugin blocklisting. | |||
* [[Firefox/Hotfix | Hotfix process documentation]] | * [[Firefox/Hotfix | Hotfix process documentation]] | ||
* [[Blocklisting|Blocklisting]] | |||
;Here are some guidelines for developers, product managers, and our team as well. | |||
* [[Release_Management/Uplift_rules|Uplift rules]] | * [[Release_Management/Uplift_rules|Uplift rules]] | ||
* [[Release_Management/Tracking_rules|Tracking rules]] | * [[Release_Management/Tracking_rules|Tracking rules]] | ||
* [[Release_Management/Relnotes_rules|Release notes rules]] | * [[Release_Management/Relnotes_rules|Release notes rules]] | ||
;Tools | |||
* [http://ship-it.mozilla.org/ Ship-it UI] - Need to be on MPT VPN | |||
* Our [[Release_Management/Release_Survey| Release Survey]] | |||
* [https://wiki.mozilla.org/User:Akeybl/Release_Dash Firefox Triage Dashboard] | * [https://wiki.mozilla.org/User:Akeybl/Release_Dash Firefox Triage Dashboard] | ||
* [ | * [[Release_Management/Onboarding | Onboarding]] | ||
;B2G pages | |||
* [https://wiki.mozilla.org/B2G/Triage B2G Triage Page] | * [https://wiki.mozilla.org/B2G/Triage B2G Triage Page] | ||
* [https://wiki.mozilla.org/Release_Management/B2G_Landing#Versions_and_Scheduling B2G Landing] | * [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) | * [https://intranet.mozilla.org/Program_Management/Firefox_OS/Localization FXOS Localizations] (auth required) | ||
[[Category:Release_Management]] | [[Category:Release_Management]] | ||
Revision as of 23:14, 11 September 2015
Quick Links
- Release Calendar
- The Release Process explained
- Current and Past Releases
- Firefox Merge/Release Calendar
- Release Calendar (Details)
About Release Management
The Release Management Team keeps the release process on track while ensuring quality releases of our products and for users. We track work for upcoming releases, coordinating with any and all teams responsible for areas of release quality, security, and stability. As release managers track specific features and individual bugs, we work with developers, engineering managers, product managers, UI/UX teams, and QE, monitoring everything that goes into a new version of Firefox under development. We aim to get features & fixes (and sometimes backouts) landed in time for proper evaluation. Our goal is to ship the most stable & quality product possible for Firefox Desktop & Mobile.
Contribute
There are many ways to help the release management team and be part of it.
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!
- Our automatic nag tool to send email to Firefox developers about their bugs
- ship-it - interface to start builds of Firefox, Firefox for Android and Thunderbird
- Google Play scripts to upload APK and manage translations
Team info
- Release_Management/Team_members List of release managers, past and present
- Release_Management/Quarterly_Goals for the relman team
Communication Channels
- Team distribution list: release-mgmt at mozilla dot com
- IRC
- #relman - Release Management specific channel
- #release-drivers - Firefox Desktop and Android release drivers
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.
- Channel Meeting
- This meeting takes place twice a week on Tuesday at 10 AM PT and Thursday at 10 AM PT in Release Coordination Vidyo Room
- Channel Meeting Wiki Archive
- Release Sign-offs
- This meeting happens a week before we are ready to ship at the Thursday Channel Meeting to address any outstanding concerns around the release
- Release sign-off meeting
- Release Post Mortem
- This meetings happens at the Tuesday Channel Meeting two weeks after a release
- Postmortem Schedule & Agenda
Calendar Updating
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
Team Resources
Each version of Firefox is follwed by a release manager who owns it from start to release (and beyond). This way, Nightly, Aurora, Beta, ESR, and Release channels have someone dedicated to getting all the pieces put together correctly.
- Release_Management/Release_owners
- Nightly Tasks for relman during Nightly
- Aurora Landing Process What we do during the Aurora cycle
- Beta Release Checklist
- ESR Triage
- Publishing to Mobile stores
- Release Days Merge and release day processes
- Releng release flow for Beta and Release
- Release managers also help with ways we can update aspects of Firefox on the fly, including add-on hotfixes, and graphics driver and plugin blocklisting.
- Here are some guidelines for developers, product managers, and our team as well.
- Tools
- Ship-it UI - Need to be on MPT VPN
- Our Release Survey
- Firefox Triage Dashboard
- Onboarding
- B2G pages
- B2G Triage Page
- B2G Landing
- FXOS Localizations (auth required)