From 995f2781149a6f48cf831ea0fe19a8a005673d91 Mon Sep 17 00:00:00 2001 From: Mo Zhu Date: Tue, 21 Mar 2023 09:07:23 -0700 Subject: [PATCH] Update release blog post process (#10642) --- handbook/product/README.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/handbook/product/README.md b/handbook/product/README.md index 8beb5692fb..52bc6dbf9b 100644 --- a/handbook/product/README.md +++ b/handbook/product/README.md @@ -167,13 +167,11 @@ After the kickoff of a product sprint, the marketing and product teams should de ### Blog post -The product team is responsible for providing the marketing team with the necessary information for writing the release blog post. Every three weeks after the sprint is kicked off, the product team meets with the relevant marketing team members to go over the features for that sprint and recommend items to highlight. +Before each release, an issue for the release post is generated by the engineering team lead, which includes a list of the *Tier 3* features included in the upcoming release. This list of features should point the reader to the GitHub issue that explains each feature in more detail. -The release blog post issue includes a list of the primary *Tier 2/3* features included in the upcoming -release. This list of features should point the reader to the GitHub issue that explains each -feature in more detail. +An example release blog post issue is [here](https://github.com/fleetdm/fleet/issues/3465). -Find an example release blog post issue [here](https://github.com/fleetdm/fleet/issues/3465). +The product team is responsible for providing the marketing team with the necessary information for writing the release blog post. Every three weeks after the sprint is kicked off, the product team meets with the relevant marketing team members to go over the features for that sprint and recommend items to highlight as Tier 2 features and provide relevant context for other features to help marketing decide which features to highlight. ### Customer announcement @@ -288,7 +286,7 @@ available in Google Drive. Directly Responsible Individuals (DRI) engage in the ritual(s) below at the frequency specified. | Ritual | Frequency | Description | DRI | -|:-----------------------------|:-----------------------------|:----------------------------------------------------|-------------------| +|:-----------------------------|:-------------------------|:----------------------------------------------------|-------------------| | 🗣 Product feature requests | 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 | | 🗣️ Product feature requests prep and cleanup | Weekly (Tuesdays) | Every week a backup doc is created to accompany the 🗣️ Product Feature Requests event | Mo Zhu | | 🗣 Product office hours | Weekly (Thursdays) | Ask questions to the product team | Mo Zhu |