Sheriffing/Schedule for Tasks performed by Code Sheriffs: Difference between revisions

add details about mozilla-beta release graph watching
(add details about mozilla-beta release graph watching)
Line 1: Line 1:
Version: 5 (Last Updated 2020-06-17)
Version: 6 (Last Updated 2020-11-03)
{| class="wikitable"
{| class="wikitable"
|-
|-
Line 34: Line 34:
# If it is resolved fixed but the widget showing the number of classifications per day still shows activity, it is used for non-trunk trees (e.g. beta, release, esrs). Keep it in that case.
# If it is resolved fixed but the widget showing the number of classifications per day still shows activity, it is used for non-trunk trees (e.g. beta, release, esrs). Keep it in that case.
|}
|}
In the nights from
* Sunday to Monday
* Tuesday to Wednesday
* Thursday to Friday
the tasks which are required to ship beta builds to users run (e.g. creating builds other than US English, creating updates and verifying their correctness).
These tasks start at 21:00 UTC (= 23:00 Romanian time in winter, 00:00 in summer).
Exceptions are:
* Sunday to Monday when Monday is merge day: the beta build starts after the merge on Monday.
* week before release: release candidates get built instead and release management starts these manually.
Sometimes these beta builds are not part of the last 10 pushes which are shown by default by Treeherder. People starting a shift during which such a "release graph" for beta is supposed to run shall load pushes for mozilla-beta until they see a push with changes affecting also the US English Firefox (= usually the pushes from release management). These should get new running tasks after the aforementioned times. For the Sunday to Monday shift, this can be a push from Friday.
Failing tasks ("UV", "c-up", "L10n" etc.) should be rerun and escalated in the [https://chat.mozilla.org/#/room/#releaseduty:mozilla.org releaseduty] channel on Matrix if they continue to fail.


====Sheriffing and quality/stability related tasks executed by one person (Aryx)====
====Sheriffing and quality/stability related tasks executed by one person (Aryx)====
Confirmed users
600

edits