Sharon Katz
7737b31069
**Related issue:** Closes #49286 # Checklist for submitter If some of the following don't apply, delete the relevant line. - ~Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`.~ N/A (handbook-only change) - [x] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented (using placeholders for values in statements), JS inline code is prevented especially for url redirects, and untrusted data interpolated into shell scripts/commands is validated against shell metacharacters. - [x] Timeouts are implemented and retries are limited to avoid infinite loops - [x] If paths of existing endpoints are modified without backwards compatibility, checked the frontend/CLI for any necessary changes ## Testing - ~Added/updated automated tests~ N/A (handbook-only change) - ~Where appropriate, automated tests simulate multiple hosts and test for host isolation~ N/A - [x] QA'd all new/changed functionality manually For unreleased bug fixes in a release candidate, one of: - ~Confirmed that the fix is not expected to adversely impact load test results~ N/A - ~Alerted the release DRI if additional load testing is needed~ N/A ## Summary Adds a "Code review coverage during time off" section to the Product groups handbook page. When a small product group (2-3 engineers) has someone on vacation, this documents the process: start with AI review, then have the EM find a temporary human reviewer from another group, preferably one the EM also manages.
Welcome to Fleet
Introduction
The Fleet handbook is the living source of truth for how we run the company. This handbook is open to the world and feedback and contributions are welcome from everyone. Feel free to click "Edit this page" to suggest an improvement anywhere you see fit. (The right reviewer will be automatically notified, and will reply to you promptly. Your change will go live on the website ≈10 minutes after it is merged.)