The Tree Sheriffs, aka Code Sheriffs
When Mozilla moved to the "inbound" model of tree management, the Tree Sheriffs became important stewards of our engineering infrastructure. The primary responsibility of the Sheriffs is to aid developers to easily, quickly, and seamlessly land their code in the proper location(s) and ensure that code does not break our automated tests. In the service of this objective, the Sheriffs work closely with the larger engineering organization to create and enforce landing policies that increase productivity while maintaining an efficient and robust automated testing system. Beyond the policy role, they have also become shepherds of automation quality by monitoring intermittent failures, performing uplifts and merges, and identifying poorly performing automation machines. A formal module for the Tree Sheriffs in the larger context of the Activities Module was created: Modules/Activities#Tree_Sheriffs.
Meet the Sheriffs
The owners & peers of the Tree Sheriffs module can be found on the module page, however for day-to-day sheriffduty coverage, look for the following people in #developers and #sheriffs. The on-duty sheriff will typically have "|sheriffduty" appended to their IRC nick.
- UTC+1: Sebastian Hengst [:Aryx] (staff/community)
- UTC-8: Phil Ringnalda [:philor] (community)
For more info on what's happening at the moment, see the current activity log: Activity Log
We're always looking for more people to join the community team and help out - just drop us a message!
- How to get started as a sheriff
- Activity Logs: Notes for sheriffs handover/current issues
- Uplift simulation reference: a list of all beta uplift simulations performed and associated bugs filed
- How-to guides
- Treeherder: how to interpret Treeherder data. Also explains how to star failures.
- Deciding To Close A Tree