Skip to content

Latest commit

 

History

History
27 lines (22 loc) · 1.46 KB

platform_reviewer_checklist.rst

File metadata and controls

27 lines (22 loc) · 1.46 KB

Platform Reviewer Checklists

There are several policies documented in :ref:`GitHub Issue Management <issues>` that the on-call platform reviewer should enforce. The on-call reviewer should run through this checklist at least once per day.

Search for issues without an assigned team and assign a team. When in doubt, seek advice on slack.

Search for issues without an assigned individual and assign an owner. When in doubt, assign :ref:`the lead <issues-team>` associated with the issue's team label.

Search for pull requests that need review and (probably) assign a feature reviewer. This is intended to make sure that requests from outside developers receive timely attention. For a pull request by a core Drake Developer, leaving it unassigned may be acceptable when it is clearly an early work-in-progress -- but if it is unassigned for several days, you should probably encourage the developer to label it "do not review" for clarity.