Clarify stable features usage

This commit helps clarify the usage of stable features to be apparent in also apis other than GA.
tektoncd · Jul 28, 2023 · 8360276 · 8360276
1 parent f5b1a3e
commit 8360276
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 4 deletions.
diff --git a/api_compatibility_policy.md b/api_compatibility_policy.md
@@ -119,9 +119,7 @@ See the current list of [alpha features](https://github.com/tektoncd/pipeline/bl
 
 ### GA/Stable features
 
-- GA/Stable features are present in a [GA CRD](#ga-crds) only.
-
-- GA/Stable features are enabled by default
+- GA/Stable features are enabled by default and cannot be disabled.
 
 - GA/Stable features will not be removed or changed in a backwards incompatible manner without incrementing the API Version.
 

diff --git a/docs/additional-configs.md b/docs/additional-configs.md
@@ -256,7 +256,7 @@ The default is `false`. For more information, see the [associated issue](https:/
 
 - `enable-api-fields`: When using v1beta1 APIs, setting this field to "stable" or "beta"
 enables [beta features](#beta-features). When using v1 APIs, setting this field to "stable"
-allows only stable features, and setting it to "beta" allows only beta features.
+allows only stable features, and setting it to "beta" allows also beta features.
 Set this field to "alpha" to allow [alpha features](#alpha-features) to be used.
 
 For example: