From 36a27fe74930464c5f1bf18d9dfaef647addf3d7 Mon Sep 17 00:00:00 2001 From: Paolo Insogna Date: Sat, 18 Apr 2026 10:01:48 +0200 Subject: [PATCH 1/2] doc: add experimental modules lifetime policy Signed-off-by: Paolo Insogna --- doc/contributing/collaborator-guide.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/doc/contributing/collaborator-guide.md b/doc/contributing/collaborator-guide.md index 99b3ec84b3b9e0..92d06307acc439 100644 --- a/doc/contributing/collaborator-guide.md +++ b/doc/contributing/collaborator-guide.md @@ -462,6 +462,15 @@ For pull requests introducing new core modules: * Land only after sign-off from at least two TSC voting members. * Land with a [Stability Index][] of Experimental. The module must remain Experimental until a semver-major release. +* Introducing an Experimental feature means taking ownership of the experiment + and committing to a clear outcome: either promoting it to stable or removing + it in a timely manner. Because experimental features can be vulnerable to + security issues, the author is also expected to help assess and patch + vulnerabilities. If an experimental feature has reached mainstream adoption such + that breaking changes are not realistically possible without ecosystem breakage, + it should be considered stable and either be promoted or be removed after a + deprecation cycle. + ### Introducing new APIs on the global scope From 15bdd1386b19ef271480d6ab8f7f2fa73dc01b9e Mon Sep 17 00:00:00 2001 From: Paolo Insogna Date: Sat, 18 Apr 2026 10:05:43 +0200 Subject: [PATCH 2/2] fixup Signed-off-by: Paolo Insogna --- doc/contributing/collaborator-guide.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/doc/contributing/collaborator-guide.md b/doc/contributing/collaborator-guide.md index 92d06307acc439..b3e201751b2280 100644 --- a/doc/contributing/collaborator-guide.md +++ b/doc/contributing/collaborator-guide.md @@ -466,12 +466,11 @@ For pull requests introducing new core modules: and committing to a clear outcome: either promoting it to stable or removing it in a timely manner. Because experimental features can be vulnerable to security issues, the author is also expected to help assess and patch - vulnerabilities. If an experimental feature has reached mainstream adoption such - that breaking changes are not realistically possible without ecosystem breakage, - it should be considered stable and either be promoted or be removed after a + vulnerabilities. If an experimental feature has reached mainstream adoption such + that breaking changes are not realistically possible without ecosystem breakage, + it should be considered stable and either be promoted or be removed after a deprecation cycle. - ### Introducing new APIs on the global scope Exposing new APIs to the global scope that are available without