empayre/fleet
14
0
Fork 0
mirror of https://github.com/empayre/fleet.git synced 2024-11-06 08:55:24 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Editor pass - Handbook: Add "Beta features" section and DRIs (#5382)

Browse Source 
Editor pass for:  https://github.com/fleetdm/fleet/pull/5336
This commit is contained in:
Desmi-Dizney 2022-04-26 17:56:53 -05:00 committed by GitHub
parent 86ddbadebe
commit 0cb06a83a7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
handbook/product.md
View File

@ -378,11 +378,11 @@ At Fleet, features are advertised as "beta" if there are concerns that the featu
deployments. For example, these concerns could be related to the feature's performance in Fleet
deployments with hundreds of thousands of hosts.
The following highlights should be considered when deciding if we promote a as "beta:"
The following highlights should be considered when deciding if we promote a feature as "beta:"
- The feature will not be advertised as "beta" permanently. This means that the individual who is directly
responsible (DRI) that a feature is advertised as "beta" is responsible for creating an issue that
explains why the feature is advertised as "beta" and tracks the feature's progress towards advertising the feature as "stable."
- The feature will not be advertised as "beta" permanently. This means that the Directly
Responsible Individual (DRI) who decides a feature is advertised as "beta" is also responsible for creating an issue that
explains why the feature is advertised as "beta" and tracking the feature's progress towards advertising the feature as "stable."
- The feature will be advertised as "beta" in the documentation on fleetdm.com/docs, release notes, release blog posts, and Twitter.
## Feature flags
@ -392,8 +392,8 @@ At Fleet, features are placed behind feature flags if the changes could affect F
The following highlights should be considered when deciding if we should leverage feature flags:
- The feature flag must be disabled by default.
- The feature flag will not be permanent. This means that the individual who is directly responsible
(DRI) that a feature flag should be introduced is responsible for creating an issue to track the
- The feature flag will not be permanent. This means that the Directly Responsible Individual
(DRI) who decides a feature flag should be introduced is also responsible for creating an issue to track the
feature's progress towards removing the feature flag and including the feature in a stable
release.
- The feature flag will not be advertised. For example, advertising in the documentation on fleetdm.com/docs, release notes, release blog posts, and Twitter.