github/falco
1
0
Fork 0
mirror of https://github.com/falcosecurity/falco.git synced 2025-09-17 07:18:26 +00:00
Code Issues Projects Releases Wiki Activity

Update proposals/20231220-features-adoption-and-deprecation.md

Browse Source 
Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
This commit is contained in:
Leonardo Grasso
2024-02-16 11:35:21 +01:00
committed by poiana
parent 3bdb98a46b
commit 63ccf872fd
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
proposals/20231220-features-adoption-and-deprecation.md
View File

@@ -115,7 +115,7 @@ The adoption policy applies to any backward compatible user-facing changes which
**Adoption rules**: **Adoption rules**:
1. A feature can be introduced at only one of the following levels: 1. A feature can be introduced at only one of the following levels:
- Sandbox: The feature must be opt-in (e.g., a feature flag), labeled as *Sandbox* and the user must be proactively informed by the experimental nature of the feature (i.e. emitting a notice when the feature is being enabled). - Sandbox: The feature must be opt-in (e.g., using a feature flag), labeled as *Sandbox* and the user must be proactively informed by the experimental nature of the feature (i.e. emitting a notice when the feature is being enabled).
- Incubating: The feature must be labeled as *Incubating*. - Incubating: The feature must be labeled as *Incubating*.
2. A feature can be promoted *from Sandbox to Incubating* or *from Incubating to Stable* only after at least one release cycle has passed without user-facing changes to the feature. 2. A feature can be promoted *from Sandbox to Incubating* or *from Incubating to Stable* only after at least one release cycle has passed without user-facing changes to the feature.
3. A feature cannot be demoted to a previous level. 3. A feature cannot be demoted to a previous level.