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

remove check for expired telemetry probes without tests attached, now covered by probe-scraper script https://bugzilla.mozilla.org/show_bug.cgi?id=1511035
(added request of new version to be added to Bugzilla and handling of expiring telemetry probes)
(remove check for expired telemetry probes without tests attached, now covered by probe-scraper script https://bugzilla.mozilla.org/show_bug.cgi?id=1511035)
Line 43: Line 43:
| version increase simulation || First Tuesday after version increase || The first time beta simulations are done after the version number got increased (usually a Tuesday), later as needed - at least a week before the next version increase to verify fixes worked and no new issues have been added.
| version increase simulation || First Tuesday after version increase || The first time beta simulations are done after the version number got increased (usually a Tuesday), later as needed - at least a week before the next version increase to verify fixes worked and no new issues have been added.
Simulate the code in mozilla-central with the next higher version number.
Simulate the code in mozilla-central with the next higher version number.
|- style="vertical-align:top"
| create bugs for expiring telemetry probes || First Wednesday after version increase
||Not every expiring browser measurement will cause test breakage. Create a bug for each group of expiring telemetry probes (group by the bugs which added or extended them according to the history annotation on the left in searchfox). Find them with an adjusted version of [https://searchfox.org/mozilla-central/search?q=expir.*74&regexp=true&path=toolkit%2Fcomponents%2Ftelemetry%2F this query].
|}
|}
Confirmed users
600

edits