Release Management/Onboarding: Difference between revisions

← Older edit

Release Management/Onboarding (view source)

Revision as of 19:24, 17 November 2025

1,551 bytes added , 17 November

fixing old links

Diannasmith

255

edits

@@ Line 8: / Line 8: @@
 * Create a [https://bugzilla.mozilla.org/createaccount.cgi Bugzilla] account.
 * File a bug to request for your bugzilla account to be added to the <code>mozilla-next-drivers</code> and <code>mozilla-stable-branch-drivers</code> groups in order to set tracking flags (eg: {{bug|962151}}). Make sure you also have the <code>edit-bugs</code> and <code>canconfirm</code> permissions.
-* You can see security sensitive bugs if someone CCs you into the bug, or if you eventually join the security group list. [https://www.mozilla.org/en-US/about/governance/policies/security-group/bugs/#expanding Security permission] comes later.
+* You can see security sensitive bugs if someone CCs you into the bug, or if you eventually join the security group list. [https://www.mozilla.org/en-US/about/governance/policies/security-group/bugs/#expanding Security permission] comes later. See [https://mana.mozilla.org/wiki/pages/viewpage.action?spaceKey=FIREFOX&title=Client+Security+Bug+Access+Policy Client Security Bug Access Policy] mana page for additional info on requesting access.
 == Internal Documentation ==
-* Ask your manager for the permissions to access the [https://drive.google.com/open?id=0B0AhJMhJM7DnbXQ0NlplR0swdjQ|shared team Google drive folder].
+* Ask your manager for the permissions to access the [https://drive.google.com/drive/folders/0B0AhJMhJM7DnbXQ0NlplR0swdjQ?resourcekey=0-Y0JOgzS9u8wDPabHQRvbLQ&usp=sharing|shared team Google drive folder].
 == VPN ==
@@ Line 17: / Line 17: @@
 '''Documentation:'''
-* [https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=30769829 VPN General Info]
+* To get access to Mozilla OpenVPN, place a request for Viscosity for Mac/PC on the [https://mozilla-hub.atlassian.net/servicedesk/customer/portal/6 JSM portal] and follow the Mac/PC installation instructions.
 * [https://mana.mozilla.org/wiki/display/SD/Viscosity+Install+for+Windows Viscosity Install for Windows]
 * [https://mana.mozilla.org/wiki/display/SD/Viscosity+Install+for+Mac Viscosity Install for Mac].
@@ Line 25: / Line 25: @@
 [https://shipit.mozilla-releng.net/ Ship It] is available behind our VPN, as is [https://balrog.services.mozilla.com balrog's admin UI].
-File a bug ([https://bugzilla.mozilla.org/enter_bug.cgi?product=Infrastructure%20%26%20Operations&component=Infrastructure%3A%20LDAP Infrastructure & Operations::Infrastructure:LDAP]) to be added to the <code>shipit</code>, <code>vpn_shipit</code>, <code>balrog</code> and <code>vpn_balrog</code> groups. Example: {{Bug|1469544}}
+File a bug ([https://bugzilla.mozilla.org/enter_bug.cgi?product=Infrastructure%20%26%20Operations&component=Infrastructure%3A%20LDAP Infrastructure & Operations::Infrastructure:LDAP]) to be added to the <code>shipit_firefox</code>, <code>shipit_mobile</code>, <code>vpn_cloudops_shipit</code>, <code>balrog</code> and <code>vpn_balrog</code> groups. Example: {{Bug|1469544}}
 Once you are using the Mozilla VPN, you can access the application and use your LDAP account to log in.
@@ Line 36: / Line 36: @@
 The [https://dashboard.snapcraft.io/snaps/firefox/  Firefox Snaps Dashboard] requires a [https://login.ubuntu.com Ubuntu One developer account] and this account to be associated with your @mozilla.com email address. Your Ubuntu One account should have 2FA activated ([https://help.ubuntu.com/community/SSO/FAQs/2FA#How_do_I_add_a_new_authentication_device_and_start_using_2-factor_authentication.3F Ubuntu Specific instructions]).
-Once you have set up your Ubuntu One account and registered as a developer on Snapcraft with this account, ask Release Engineering (currently specifically Johan Lorenzo) to send you an invite to manage Firefox snaps. The Snap uploading process was defined in {{Bug|1467261}}.
+Once you have set up your Ubuntu One account and registered as a developer on Snapcraft with this account, ask Release Engineering  to send you an invite to manage Firefox snaps. An unfinished stab at defining the Snap uploading process is in {{Bug|1467261}}.  Anyone who is on the list at https://dashboard.snapcraft.io/snaps/firefox/collaboration/ can add someone else to the list.
+== Samsung Store ==
+You will need to ask for access to the [https://account.samsung.com/accounts/v1/MBR/signInGate?locale=en_US&countryCode=US&goBackURL=https:%2F%2Faccount.samsung.com%2Fmembership%2Fintro&returnURL=https:%2F%2Faccount.samsung.com%2Fmembership%2Fintro&redirect_uri=https:%2F%2Faccount.samsung.com%2Fmbr-svc%2Fauth%2FregistAuthentication&tokenType=OAUTH&response_type=code&client_id=k2jxgrvd6k&state=FZCyUxHKqJUDlXilPsAYuQElMtpvHEwu Samsung Store]
 == Release Notes ==
@@ Line 46: / Line 49: @@
 == Google Play Console ==
-Ask your manager to add you.
+File a bug in the App Stores component, https://bugzilla.mozilla.org/enter_bug.cgi?product=App%20Stores
+Example: https://bugzilla.mozilla.org/show_bug.cgi?id=1724432
 == Socorro/Stability (crash-stats) ==
+* [https://bluesock.org/~willkg/blog/mozilla/socorro_overview_2021.html This blog post] provides an overview of Mozilla's crash reporting pipeline.
 * https://crash-stats.mozilla.org/ should be accessible for general use. If you require enhanced permissions (typically to [https://crash-stats.mozilla.org/documentation/protected_data_access/ access protected data], file a bug in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Socorro Socorro | General].
-* [https://missioncontrol.telemetry.mozilla.org/#/?channel=release Mission Control] is the dashboard we use for crash monitoring and to report at the Channel and Cross Functional Meetings.  [https://metrics.mozilla.com/public/sguha/mc2/missioncontrol_v2.html Mission Control v2] is the newer version.
+* there is more crash info at https://mozilla.cloud.looker.com/dashboards/918?Channel=release&OS+Name=&Ten+Percent+Sample=Yes   But no special account is needed.
-== Trello ==
-Trello is used to track the shipping of Firefox features in the [https://trello.com/b/8k1hT2vh/firefox Firefox Trello Board]. Ask Thomas Elin for access.
-Each release has its own column listing the features planned for that specific version. Pro tip: subscribe to a column notification to receive updates given to all the cards in that column.
-Our team also has a [https://trello.com/b/D5vYvuGP/release-management Trello board ] but we currently do not use it.
 == Github ==
@@ Line 77: / Line 75: @@
 == Other ==
 * This wiki! [[Special:RequestAccount | Create an account]] and update the [[Release_Management/Team_members | team members page]].
+* Once you are familiar with the release checklists, it will be extremely useful to read this [https://wiki.mozilla.org/Release_Management/Release_Process_Checklist_Documentation#Beta_Checklist documentation] on what each step means since the checklists are shorthanded
+* A lot of names will be thrown around the first couple of months, here is a list of common [https://firefox-source-docs.mozilla.org/contributing/pocket-guide-shipping-firefox.html#definitions definitions.]
+* Things to Bookmark
+** Bugzilla [https://trainqueries.herokuapp.com/ Queries]
+** Current Firefox trains: https://whattrainisitnow.com/
 = Communication Channels =
 == Release Calendar ==
-This page describes our release schedule: [[Release_Management/Calendar | Firefox Release Calendar]]. You should add these to your regular Google calender so you can easily see the state of any release.
+This page describes our release schedule: [[Release_Management/Calendar | Firefox Release Calendar]]. You should add these to your regular Google calendar so you can easily see the state of any release. Click through on the links below and then hit the + button at bottom right to add this to your Mozilla Google calendar.
 * This is the basic public calendar with release dates: https://www.google.com/calendar/embed?src=mozilla.com_2d37383433353432352d3939%40resource.calendar.google.com
 * This is the release manager team with tons of detail: https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ - This is really helpful for the first managed release cycle.
@@ Line 92: / Line 95: @@
 ''' Other useful lists '''
 You'll need to manually subscribe to:
-* [https://mail.mozilla.org/listinfo/release-drivers release-drivers]
+* [https://groups.google.com/a/mozilla.org/g/release-drivers release-drivers]
-* [https://lists.mozilla.org/listinfo/dev-platform mozilla.dev.platform]
+* [https://groups.google.com/a/mozilla.com/g/release-notes release-notes]
-* [https://mail.mozilla.org/listinfo/enterprise Enterprise]
+* [https://groups.google.com/a/mozilla.org/g/release-signoff release-signoff]
-* [https://mail.mozilla.org/listinfo/stability Stability]
+* [https://groups.google.com/a/mozilla.org/g/release Release-mgmt]
-* [https://groups.google.com/a/mozilla.com/group/release-automation-notifications/ release-automation-notifications] (Contributors need aninvite)
+* [https://groups.google.com/a/mozilla.org/g/dev-platform dev-platform]
-* [https://mail.mozilla.org/listinfo/security-group security-group] Check out the [https://www.mozilla.org/en-US/about/governance/policies/security-group/membership/ policy] for getting added to the security-group list.
+* [https://groups.google.com/a/mozilla.org/g/enterprise Enterprise]
+* [https://groups.google.com/a/mozilla.org/g/stability Stability]
-These are available as [news://news.mozilla.org nntp newsgroups], [https://groups.google.com/forum/#!overview Google groups], and [https://lists.mozilla.org/listinfo mailing](1), [https://mail.mozilla.org/ lists](2).
+* [https://groups.google.com/a/mozilla.org/g/announce Announce]
+* [https://groups.google.com/a/mozilla.org/g/security-group security-group] Check out the [https://www.mozilla.org/en-US/about/governance/policies/security-group/membership/ policy] for getting added to the security-group list.
+* [https://groups.google.com/a/mozilla.com/g/funstuff Funstuff]
 == Websites ==
@@ Line 106: / Line 111: @@
 == Matrix ==
-We hang out in the <code>#release-drivers:mozilla.org</code> and <code>#releaseduty:mozilla.org</code> channels.
+We hang out in the <code>#release-discussions:mozilla.org</code> and <code>#releaseduty:mozilla.org</code> channels.
 The following can also be useful:
-- <code>#developers:mozilla.org</code>
+* <code>#developers:mozilla.org</code>
-- <code>#firefox-ci:mozilla.org</code>
+* <code>#firefox-ci:mozilla.org</code>
-- <code>#sheriffs:mozilla.org</code>
+* <code>#sheriffs:mozilla.org</code>
 == Slack ==
 [https://mozilla.slack.com/ Mozilla Slack], you can login with [https://sso.mozilla.org sso].
-* <code>release-drivers</code> - release related discussions
+* <code>bmo</code> - All things bugzilla
+* <code>firefox</code> - firefox development room
+* <code>firefox-ios-releases</code> - iOS release related discussions
+* <code>fx-weekly-digest</code> - Where the weekly digest is posted and updated
 * <code>qa-coordination</code> - QE team channel
+* <code>moco</code> - backchannel for meetings
 * <code>release-coordination</code> - Cross functional coordination room during a release
-* <code>triage-and-tracking</code> - All things bugzilla
+* <code>release-mgmt</code>- Relman team channel
 * <code>release-notes</code> - coordination with release notes stakeholders, marketing and writers
-* <code>moco</code> - backchannel for meetings
-* <code>firefox</code> - firefox development room
-* <code>planning</code>- backchannel for weekly Cross Functional Meeting
 == Meetings ==
@@ Line 129: / Line 135: @@
 '''Tuesday:'''
-* 1st Channel meeting
+* Triage meeting
 '''Wednesday'''
-* Cross Functional meeting
+* Our Team meeting
 '''Thursday'''
-* 2nd Channel meeting
+* Channel meeting
-* Our Team meeting
 Ask your manager and colleagues to invite you to these meetings.
-== EtherPad ==
-EtherPad is a great tool for dynamic collaboration during meetings, brainstorming, or other times when you need to collaborate:
-* https://pad.mozilla.org/ for general use
-* https://pad.mozilla.org/p/channel-meeting for release information
 == Pastebin ==
-There's a local pastebin instance at https://paste.mozilla.org/, so you don't need to paste multi-lines into a channel. Use this handy [https://hg.mozilla.org/build/braindump/file/tip/utils/pastebin helper script] to pipe to pastebin from terminal.
+There's a local pastebin instance at https://paste.mozilla.org/, so you don't need to paste multi-lines into a channel.  You can use <code>mach pastebin</code> to paste from a terminal.
-    it creates a new page from stdin, and outputs the url to stdout
-    an argument will be interpretted as the syntax highlighting format to use
-    sample usage: hg diff | pastebin python | pbcopy (last part mac specific)
-    set & export PASTEBIN_NAME if you don't want to post as anonymous.
 == Planet ==
@@ Line 156: / Line 151: @@
 = Software =
 == Firefox ==
-# Please download & install Firefox [https://nightly.mozilla.org nightly], [https://beta.mozilla.org beta] and [https://firefox.com release]
+# Please download & install Firefox [https://nightly.mozilla.org nightly], [https://beta.mozilla.org beta], [https://firefox.com release], and [https://www.mozilla.org/en-US/firefox/developer/ devedition]
 # [https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles#w_creating-a-profile Create new profiles] for each version + your own profile. Read [https://developer.mozilla.org/en-US/docs/Mozilla/Multiple_Firefox_Profiles Multiple Firefox Profiles] for more help with the profile manager.
@@ Line 176: / Line 171: @@
 === Reports ===
-* [https://bugzilla.mozilla.org/page.cgi?id=release_tracking_report.html release tracking report]
+* [https://bugzilla.mozilla.org/page.cgi?id=release_tracking_report.html release tracking report] (builds bugzilla queries for uplifts)
 === Queries ===
 In your bugzilla preferences, under Saved Searches, you can add some of the following to your footer for quick access:
@@ Line 192: / Line 188: @@
 == Repos to check out if you are going to develop ==
 * [https://github.com/mozilla/relman-auto-nag Bugzilla nag tool]
-* [https://github.com/mozilla/ship-it/ ship-it]
+* [https://github.com/mozilla-releng/shipit/ ship-it]
 * [https://github.com/mozilla/rna Nucleus]
 * [https://github.com/mozilla/bedrock Bedrock] Mozilla website
 * [http://harthur.github.io/mozregression/ mozregression]
-* [https://github.com/mozilla-releng/mozapkpublisher/ mozapkpublisher]
 == Helpful webextensions ==
@@ Line 215: / Line 210: @@
 * [[Release_Management/Queries|All Queries]]
 * [[RapidRelease/LandingPlan|Landing Plan]]
-* [[Release_Management/aurora_Landing_Process|Aurora/DevEdition Landing Process]]
 * Article on our release process in [http://www.drdobbs.com/architecture-and-design/firefox-release-engineering/240168409 Dr. Dobbs] (mostly still true)
 = Fun Tips & Tricks =
-== Subcribe to fun stuff ==
+== Subscribe to fun stuff ==
-* Request here https://bugzilla.mozilla.org/show_bug.cgi?id=391268
+* See [https://wiki.mozilla.org/Release_Management/Onboarding#E-Mail Email] groups "Fun Stuff" above to self-subscribe
+= Overview Summary of Role =
+* It would help to imagine the Relman role as a manager of three stages. Imagine a kanban with three columns where each stage is a column. Each stage is a cycle of the release process. (Nightly, Beta, Release). A Relman is assigned a release (#). You see that release (#) through each column(stage). Each column has different dates, similar processes(some automated some manual), different dates, and different level of critical tasks. To ensure nothing is forgotten, we follow checklists which change depending on which stage you are in as well as which part of the stage you are in (beginning/end).
+* Must Read: [https://wiki.mozilla.org/Release_Management/Release_Process Release Process]
 [[category:Release_Management|O]]