Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 08:58:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 111

Clarify bug prioritization process (#12071)

Browse source
This commit is contained in:
Luke Heath 2023-05-31 15:29:14 -05:00 committed by GitHub
parent c7488663f2
commit 0c66a09797
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
handbook/product/README.md
View file

@ -82,6 +82,8 @@ Product Managers prioritize all potential product improvements worked on by cont
Bugs are always prioritized. (Fleet takes quality and stability [very seriously](https://fleetdm.com/handbook/company/why-this-way#why-spend-so-much-energy-responding-to-every-potential-production-incident).)
If a bug is unreleased or [critical](https://fleetdm.com/handbook/engineering#critical-bugs), it is addressed in the current sprint. Otherwise, it may be prioritized in the sprint backlog for the next sprint. Bugs are never carried more than one sprint.
> Anyone can [suggest improvements](#intake).
## Writing user stories