Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-22 16:39:01 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 121

Update release blog post process (#10642)

Browse source
This commit is contained in:
Mo Zhu 2023-03-21 09:07:23 -07:00 committed by GitHub
parent 94085da058
commit 995f278114
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
handbook/product/README.md
View file

@ -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 |