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

Jump to navigation Jump to search
add tasks performed by sheriffing lead around merge day
(change version increase simulation schedule from first to second Tuesday after version number got increased)
(add tasks performed by sheriffing lead around merge day)
Line 1: Line 1:
Version: 3 (Last Updated 2019-09-25)
Version: 4 (Last Updated 2020-02-11)
{| class="wikitable"
{| class="wikitable"
|-
|-
Line 36: 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"
| 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.
|}
====Sheriffing and quality/stability related tasks executed by one person (Aryx)====
{| class="wikitable"
|-
! Task !! Schedule !! Details
|- style="vertical-align:top"
| Create new beta simulation document|| Monday on which version got increased
||Clone the current beta simulation document, adjust versions and dates and send it to code sheriffs and release management.
|- style="vertical-align:top"
|- 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.
| 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.
Line 41: Line 53:
# 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].
# 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"
|- style="vertical-align:top"
| 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.
| Add new version to tree statistics || Monday on which version got increased
Simulate the code in mozilla-central with the next higher version number.
||Tool which shows how often and how long the trees got closed
* [https://github.com/Archaeopteryx/treestats code]
* [https://github.com/Archaeopteryx/treestats tool]
|- style="vertical-align:top"
| Last cycle quality metrics || Monday on which version got increased
||Accumulate weekly quality metrics for last release cycle
|- style="vertical-align:top"
| New Nightly respin statistics || Monday on which version got increased
||Set up new sheet to track backouts from mozilla-central and Nightly respins
|}
|}
Confirmed users
611

edits

Navigation menu