193
edits
Release Management/Nightly Respin: Difference between revisions
Adding Communication for Mobile
Diannasmith (talk | contribs) (small tweak to summary) |
Diannasmith (talk | contribs) (Adding Communication for Mobile) |
||
| Line 109: | Line 109: | ||
====Mobile==== | ====Mobile==== | ||
Once a major regression is identified, we should communicate this to the right party or team about the situation along with a plan of mitigation. Include the affected population or set forth a plan to investigate this metric. Be sure to tag mobile managers via Slack when communicating the problem. In case of an emergency or if immediate escalation is required, use Mozilla People resources to contact the Mobile Managers. | |||
The main communication channels for mobile nightly to communicate a regression are our [https://matrix.to/#/#nightly:mozilla.org #Fenix] chatroom on Matrix/Element and our #Mobile-Android-Team Slack channels | |||
[[Category:Release_Management]] | [[Category:Release_Management]] | ||
[[Category:Release_Management:Processes|Nightly Respin]] | [[Category:Release_Management:Processes|Nightly Respin]] | ||