From 7a9e46040e37ad7c2a9ad2cb335380a01013f01d Mon Sep 17 00:00:00 2001 From: Luke Heath Date: Tue, 18 Nov 2025 13:03:38 -0600 Subject: [PATCH] Update quality assurance and bug handling sections (#35922) --- handbook/company/product-groups.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/handbook/company/product-groups.md b/handbook/company/product-groups.md index 7ba6aa0f39..7818c2312a 100644 --- a/handbook/company/product-groups.md +++ b/handbook/company/product-groups.md @@ -553,6 +553,7 @@ Just as when a feature request is not accepted in the 🎁🗣 Feature Fest meet ## Quality + The goal of quality assurance is to identify corrections and optimizations before release by verifying; - Bugs - Fixes for bugs @@ -630,6 +631,8 @@ If a bug meets the criteria for a [critical bug](https://fleetdm.com/handbook/co A bug is in engineering after it has gone through product drafting, has received an estimation, and has been moved to a release board during sprint planning. +If this is a customer-reported bug that is related to performance at scale, it must be reproduced in a load test environment before a Fleet release can be published containing a fix. Request review of relevant production data to determine what changes are necessary in our load test environment's data set to reproduce the bug. If there is an ongoing outage, a hotfix branch may be deployed without load testing reproduction if approved by the relevant EM. + #### Awaiting QA