From 61038bf1b825b21b8a7fccfb5ad3487bd23333c6 Mon Sep 17 00:00:00 2001 From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com> Date: Wed, 18 Dec 2024 14:02:40 -0500 Subject: [PATCH] Handbook: make sure changes outside of product groups are QA'd (#24847) --- handbook/company/product-groups.md | 1 + 1 file changed, 1 insertion(+) diff --git a/handbook/company/product-groups.md b/handbook/company/product-groups.md index 81d6f870f82c..0482a6d8cf6f 100644 --- a/handbook/company/product-groups.md +++ b/handbook/company/product-groups.md @@ -81,6 +81,7 @@ To make a change to Fleet: - Then, it will be [drafted](https://fleetdm.com/handbook/company/product-groups#drafting) (planned). - Next, it will be [implemented](https://fleetdm.com/handbook/company/product-groups#implementing) and [released](https://fleetdm.com/handbook/engineering#release-process). +> Occasionally, a contributor outside of the [product groups](https://fleetdm.com/handbook/product-groups#current-product-groups) (open source contributor, member of the Customer Success team, etc.) will implement a change that was prioritized and drafted. On the user story for these changes, add the product group label (e.g. `#g-endpoint-ops`, `#g-mdm`), the `:release` label, and notify the product group's Engineer Manager to make sure the changes go through testing (QA) before release. ### Planned and unplanned changes