When we moved to the "inbound" model of tree management, the Tree
Sheriffs became a crucial part of our engineering infrastructure. The
primary responsibility of the Sheriffs is and will always be 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. This role has proven successful, and it
feels like it is time to propose a formal module for the Tree Sheriffs
in the larger context of the Activities Module.
Ed Morley(edmorley)will be module owner for Tree Sheriffing.
The peers will be Ryan VanderMeulen (RyanVM), Phil Ringnalda (Philor),
Carsten Book (Tomcat), and Wes Kocher (KWierso).
The living document of Sheriff roles and responsibilities will be kept
up to date on this wiki page [1] and will certainly change over time as
our organization and our automation continues to expand. But this
module and this document will help give the sheriffs a platform to work
from for future changes.
Please congratulate them all on a job well done this last year, and let
me know if you have any feedback concerning creating this new module.
Thanks,
Clint
[1] https://wiki.mozilla.org/Sheriffing
_______________________________________________
governance mailing list
[email protected]
https://lists.mozilla.org/listinfo/governance
