Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 00:49:03 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 106

Remove customer announcement process (#10747)

Browse source
This commit is contained in:
Mo Zhu 2023-03-24 10:28:13 -07:00 committed by GitHub
parent 5e27844fa2
commit e367c77246
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
handbook/product/README.md
View file

@ -67,8 +67,6 @@ What happens during emergency drafting?
2. Drafts are updated to cover edge cases or reduce functionality.
3. UI changes [are approved](https://fleetdm.com/handbook/company/development-groups#drafting-process), and the UI changes are brought back to the engineering team to continue the development task.
## Outside contributions
[Anyone can contribute](https://fleetdm.com/handbook/company#openness) at Fleet, from inside or outside the company. Since contributors from the wider community don't receive a paycheck from Fleet, they work on whatever they want.
@ -79,7 +77,6 @@ Thus, it is still important to ensure consistency, completeness, and secure deve
- Prior to merging any change, small or large, that would change the expected behavior of the product, [prioritized](#prioritizing-improvements) by the [appropriate product group's](https://fleetdm.com/handbook/company/development-groups#current-product-groups) Product Manager and [drafted](https://fleetdm.com/handbook/company/development-groups#drafting) by the group's Product Designer prior to merging.
- All changes to the user interface should be [wireframed first](https://fleetdm.com/handbook/company/why-this-way#why-do-we-use-a-wireframe-first-approach) by the appropriate Product Designer.
## Prioritizing improvements
Product Managers prioritize all potential product improvements worked on by contributors inside the company. This includes features, bug fixes, and technical debt or other contributor experience improvements.
@ -206,17 +203,6 @@ Before each release, the Head of Product [creates a "Release" issue](https://git
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 _echelon 2_ features and provide relevant context for other features to help marketing decide which features to highlight.
### Customer announcement
The product team is responsible for providing the [customer success team](../customers/README.md) with the necessary information
for writing a release customer announcement. This is accomplished by filing a release customer announcement issue and adding
the issue to the customer success board on GitHub.
The release blog post issue is filed in the private fleetdm/confidential repository because the
comment section may contain private information about Fleet's customers.
Find an example release customer announcement blog post issue [here](https://github.com/fleetdm/confidential/issues/747).
## Feature flags
At Fleet, features are placed behind feature flags if the changes could affect Fleet's availability of existing functionalities.