From ca4d7e23cb60d429de17a90be39eb478aff6fd0a Mon Sep 17 00:00:00 2001 From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com> Date: Fri, 4 Nov 2022 11:54:45 -0400 Subject: [PATCH] In handbook, update product and engineering rituals (#8582) - Remove old product rituals - Move release testing rituals to engineering handbook --- handbook/engineering/README.md | 2 ++ handbook/product/README.md | 5 ----- 2 files changed, 2 insertions(+), 5 deletions(-) diff --git a/handbook/engineering/README.md b/handbook/engineering/README.md index 4fc0898e4b..bb93c038ff 100644 --- a/handbook/engineering/README.md +++ b/handbook/engineering/README.md @@ -868,6 +868,8 @@ The following rituals are engaged in by the directly responsible individual (DRI | Release ritual | Every three weeks | Go through the process of releasing the next iteration of Fleet. | Zach Wasserman | | Create patch release branch | Every patch release | Go through the process of creating a patch release branch, cherry picking commits, and pushing the branch to github.com/fleetdm/fleet. | Luke Heath | | Bug review | Weekly | Review bugs that are in QA's inbox. | Reed Haynes | +| Release testing/QA | Every three weeks | Every release cycle, by end of day Wednesday of release week, all issues move to "Ready for release" on the ๐Ÿš€Release board. | Reed Haynes | +| Release testing/QA report | Every three weeks | Every release cycle, on the Monday of release week, the (DRI for the release ritual)[https://fleetdm.com/handbook/engineering#rituals] is updated on status of testing. | Reed Haynes | ## Fleet Sandbox Oncall diff --git a/handbook/product/README.md b/handbook/product/README.md index b37c77b94b..25f42f43d4 100644 --- a/handbook/product/README.md +++ b/handbook/product/README.md @@ -374,14 +374,9 @@ Directly Responsible Individuals (DRI) engage in the ritual(s) below at the freq | Ritual | Frequency | Description | DRI | |:-----------------------------|:-----------------------------|:----------------------------------------------------|-------------------| -| ๐ŸŽ™ Product huddle | Daily | We discuss "In progress" issues and place any issues that are "ready for review" on the list for the product design review call. On Mondays, issues are broken down into a week's work and added into "ready." We move issues out of "delivered" every Friday. | Noah Talerman | | ๐Ÿ—ฃ Product office hours | Weekly (Tuesdays) | We make a decision regarding which customer and community feature requests can be committed to in the next six weeks. We create issues for any requests that don't already have one. | Mo Zhu | -| ๐ŸŽจ UI/UX huddle | Weekly (Wednesdays) | We discuss "In progress" issues and place any issues that are "ready for review" on the list for the product design review call. We hold separate times for ๐ŸŽ™ Product huddle so Mike Thomas can make it. | Noah Talerman | | โœจ Product design review | Weekly (Thursdays) | The Product team discusses "ready for review" items and makes the decision on whether the UI changes are ready for engineering specification and later implementation. | Noah Talerman | -| ๐Ÿ‘€ Product review | Every three weeks | Fleeties present features and improvements in the upcoming release. A discussion is held about bugs, fixes and changes to be made prior to release. | Noah Talerman | | Product office hours doc prep | Weekly | Every week a backup doc is created to accompany the Product office hours event | Mo Zhu | -| Release testing/QA | Every three weeks | Every release cycle, by end of day Wednesday of release week, all issues move to "Ready for release" on the ๐Ÿš€Release board. | Reed Haynes | -| Release testing/QA report | Every three weeks | Every release cycle, on the Monday of release week, the (DRI for the release ritual)[https://fleetdm.com/handbook/engineering#rituals] is updated on status of testing. | Reed Haynes | ## Slack channels