Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-24 01:18:42 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 84

Update quality assurance and bug handling sections (#35922)

Browse source
This commit is contained in:
Luke Heath 2025-11-18 13:03:38 -06:00 committed by GitHub
parent e1e509db1d
commit 7a9e46040e
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
handbook/company/product-groups.md
View file

@ -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