From a983631aaf8d4bf46cc7c4ca8793c1dd9b97c7be Mon Sep 17 00:00:00 2001 From: Reed Haynes Date: Tue, 18 Jul 2023 12:08:53 -0500 Subject: [PATCH] Update README.md community ticket timelines (#12826) Update documentation on handling community bug reports. We will be notifying and then closing tickets at 2 and 4 week intervals instead of the previous 3 and 6 week schedule. --- handbook/engineering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/handbook/engineering/README.md b/handbook/engineering/README.md index 8f73f27e11..d2b0476a6b 100644 --- a/handbook/engineering/README.md +++ b/handbook/engineering/README.md @@ -490,7 +490,7 @@ When a new bug is created using the [bug report form](https://github.com/fleetdm At this state, the [bug review DRI](#rituals) (QA) is responsible for going through the inbox and documenting reproduction steps, asking for more reproduction details from the reporter, or asking the product team for more guidance. QA has one week to move the bug to the next step (reproduced). -For community-reported bugs, this may require QA to gather more information from the reporter. QA should reach out to the reporter if more information is needed to reproduce the issue. Reporters have six weeks to provide follow-up information for each report. We'll ping them again as a reminder at three weeks. After six weeks, we'll close the bug to remove it from our visibility, but reporters are welcome to re-open and provide context. +For community-reported bugs, this may require QA to gather more information from the reporter. QA should reach out to the reporter if more information is needed to reproduce the issue. Reporters are encouraged to provide timely follow-up information for each report. At two weeks since last communication QA will ping the reporter for more information on the status of the issue. After four weeks of stale communication QA will close the issue. Reporters are welcome to re-open the closed issue if more investigation is warranted. Once reproduced, QA documents the reproduction steps in the description and moves it to the reproduced state. If QA or the engineering manager feels the bug report may be expected behavior, or if clarity is required on the intended behavior, it is assigned to the group's product manager. [See on GitHub](https://github.com/fleetdm/fleet/issues?q=archived%3Afalse+org%3Afleetdm+is%3Aissue+is%3Aopen+label%3Abug+label%3A%3Areproduce+sort%3Acreated-asc+).