Confirmed users
609
edits
Sheriffing/Schedule for Tasks performed by Code Sheriffs: Difference between revisions
Jump to navigation
Jump to search
Sheriffing/Schedule for Tasks performed by Code Sheriffs (view source)
Revision as of 17:04, 2 January 2020
, 2 January 2020added request of new version to be added to Bugzilla and handling of expiring telemetry probes
(remove mozilla-central to mozilla-beta merges, there is only one of these merges per release cycle now and it's performed by RelEng) |
(added request of new version to be added to Bugzilla and handling of expiring telemetry probes) |
||
| Line 30: | Line 30: | ||
| beta-as-release simulation || Weekly during the Thursday night shift | | beta-as-release simulation || Weekly during the Thursday night shift | ||
||Simulate the code in mozilla-beta as mozilla-release | ||Simulate the code in mozilla-beta as mozilla-release | ||
|- style="vertical-align:top" | |- style="vertical-align:top" | ||
| Clean up list of bugs which don’t get suggested || Weekly | | Clean up list of bugs which don’t get suggested || Weekly | ||
| Line 39: | Line 36: | ||
# If the bug has been resolved as incomplete, remove it from the document. | # If the bug has been resolved as incomplete, remove it from the document. | ||
# 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. | ||
|- style="vertical-align:top" | |||
| Request new version to be added to Bugzilla || Monday before next version increase || The Gecko and Firefox version will get increased and bugs cannot be set as fixed in the new version with the [https://bugherder.mozilla.org/ Bugherder] tool until the version got added to bugzilla.mozilla.org. The new version gets requested one week in advance to allow easier coordination with the Bugzilla team. | |||
[https://bugzilla.mozilla.org/show_bug.cgi?id=1606669 Example bug] | |||
# 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. | |||
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®exp=true&path=toolkit%2Fcomponents%2Ftelemetry%2F this query]. | |||
|} | |} | ||