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

Sheriffing/Schedule for Tasks performed by Code Sheriffs (view source)

175 bytes added , 11 February 2020

change version increase simulation schedule from first to second Tuesday after version number got increased

Confirmed users

600

edits

@@ Line 41: / Line 41: @@
 # Clone [https://bugzilla.mozilla.org/buglist.cgi?list_id=15051791&short_desc=add%20gecko&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&classification=Other&chfield=%5BBug%20creation%5D&query_format=advanced&chfieldfrom=80d&short_desc_type=allwordssubstr&component=Administration&product=bugzilla.mozilla.org the bug which added the latest version to Bugzilla].
 |- style="vertical-align:top"
-| 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 || Second Tuesday after version increase || The first time a version increase simulations is done is the second Tuesday after the version number got increased (to let [https://github.com/mozilla/probe-scraper probe-scraper] alert for expiring probes before and reduced the failures in the version increase simulation), 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.
 |}