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

→‎Sheriffing and quality/stability related tasks executed by one person (Aryx): drop central-as-beta statistics for cycle as duty, on pause until needed, could check recent cycles if needed
(add note to skip beta-as-release simulation in last week of development cycle (when beta already got merged to release))
(→‎Sheriffing and quality/stability related tasks executed by one person (Aryx): drop central-as-beta statistics for cycle as duty, on pause until needed, could check recent cycles if needed)
 
Line 88: Line 88:
| Increase simulation version numbers || Monday on which version got increased
| Increase simulation version numbers || Monday on which version got increased
||Increment version numbers for central-as-beta and beta-as-release simulations at [[Sheriffing/How To/Beta simulations]]
||Increment version numbers for central-as-beta and beta-as-release simulations at [[Sheriffing/How To/Beta simulations]]
|- style="vertical-align:top"
| Last cycle central-as-beta metrics || Monday on which version got increased or soon after
||Accumulate central-as-beta and version increase metrics: how many issues got detected, what is the average time to fix them broken down by build vs test failure
|- style="vertical-align:top"
|- style="vertical-align:top"
| New Nightly respin statistics || Monday on which version got increased
| New Nightly respin statistics || Monday on which version got increased
||Set up new sheet to track backouts from mozilla-central and Nightly respins
||Set up new sheet to track backouts from mozilla-central and Nightly respins
|- style="vertical-align:top"
|- style="vertical-align:top"
| Land patches || several times per day
| Land patches || daily
||Check for patches waiting to land  
||Check for patches waiting to land  
|}
|}
Confirmed users
571

edits