Release Management: Difference between revisions

← Older edit

Release Management (view source)

Revision as of 12:36, 29 March 2023

46 bytes removed , 29 March 2023

m

Link update

Pascalc

Confirmed users

1,255

edits

@@ Line 2: / Line 2: @@
 [[File:All-firefox-logos.png|500px|center]]
 =Quick Links=
-* [[Release_Management/Calendar | Release Calendar overview ]]
+* [https://whattrainisitnow.com/calendar/ Release Calendar overview ]
 * The [[Release_Management/Release_Process | Release Process]] explained
 * [[Releases | Current and Past Releases]]
@@ Line 11: / Line 11: @@
 = 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.
+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.
-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
-* Google Play scripts to [https://github.com/mozilla-releng/mozapkpublisher/ upload the APK and manage translations]
 = Team info =
@@ Line 27: / Line 22: @@
 * Team distribution list: release-mgmt at mozilla dot com
-;IRC
+;Matrix
-* [irc://irc.mozilla.org/release-drivers #release-drivers] - Firefox Desktop and Android release drivers. Good way to contact release managers, ask questions, escalate issues.
+* [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
 * [https://twitter.com/MozillaReleases @MozillaReleases] Release Management team communication channel
-* [https://twitter.com/FirefoxNightly @FirefoxNightly]  Firefox Nightly communication and feeback 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]
-;Visio
-* [https://v.mozilla.com/flex.html?roomdirect.html&key=EXysadF68Dac Release Coordination Vidyo Link]
 ;Slack
@@ Line 48: / Line 41: @@
 * Channel Meeting
-**This meeting takes place twice a week on Tuesdays 10am Pacific time (18h UTC) and Thursdays at 8am Pacific time (16h UTC) in the [https://v.mozilla.com/flex.html?roomdirect.html&key=EXysadF68Dac Release Coordination] Vidyo Room
+** This meeting takes place twice a week on Tuesdays 10am Pacific time and Thursdays at 8am Pacific time
 ** [https://wiki.mozilla.org/Firefox/Channels/Meetings Channel Meeting Wiki Archive]
 * 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_{{Version/Gecko/release/current}}.0 Postmortem Schedule & Agenda]
@@ Line 68: / Line 61: @@
 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]].
-==Team Resources==
+==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.
 * [[Release_Management/Release_owners|Release Owners]]
-* [[Release_Management/Nightly|Nightly]] Tasks for relman during Nightly
+* [[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/Beta_Release_Checklist|Beta 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]
 * [[Release_Management/Mobile_Publishing_Documentation|Publishing to Mobile stores]]
 * [[Release Management/Release Days|Release Days]] Merge and release day processes
-* Point releases and chemspills
+* [[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
 * [https://mozilla.github.io/delivery-dashboard/ Delivery Dashboard]
-* [https://missioncontrol.telemetry.mozilla.org/ Mission Control]
 * [[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]
@@ Line 90: / Line 81: @@
 * [https://sql.telemetry.mozilla.org/dashboard/release-management-dashboard Stability dashboard]
 * [https://mozilla.github.io/stab-crashes Stability deep-dive scripts]
-* [https://www.flickr.com/photos/lizhenry/24368249885 Dashboard the Cat] - she likes to eat headphones
+* [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.
 ;Release managers also help with ways we can update aspects of Firefox on the fly, including graphics driver and plugin blocklisting.
@@ Line 98: / Line 91: @@
 ;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]]
@@ Line 104: / Line 99: @@
 ;Tools
-* [https://ship-it.mozilla.org/ Ship-it UI] - [https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=30769829 Mozilla VPN]
+* [https://shipit.mozilla-releng.net/ Ship-it UI] - [https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=30769829 Mozilla VPN]
-* [https://aus4-admin.mozilla.org/ Balrog admin UI] - requires 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]]