Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 40a4337

Browse filesBrowse files
ShogunPandaaduh95
authored andcommitted
doc: add experimental modules lifetime policy
Signed-off-by: Paolo Insogna <paolo@cowtech.it> PR-URL: #62753 Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com> Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Richard Lau <richard.lau@ibm.com> Reviewed-By: Filip Skokan <panva.ip@gmail.com>
1 parent 1eedbdd commit 40a4337
Copy full SHA for 40a4337

1 file changed

+8Lines changed: 8 additions & 0 deletions

File tree

Expand file treeCollapse file tree
Open diff view settings
Filter options
Expand file treeCollapse file tree
Open diff view settings
Collapse file

‎doc/contributing/collaborator-guide.md‎

Copy file name to clipboardExpand all lines: doc/contributing/collaborator-guide.md
+8Lines changed: 8 additions & 0 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -462,6 +462,14 @@ For pull requests introducing new core modules:
462462
* Land only after sign-off from at least two TSC voting members.
463463
* Land with a [Stability Index][] of Experimental. The module must remain
464464
Experimental until a semver-major release.
465+
* Introducing an Experimental feature means taking ownership of the experiment
466+
and committing to a clear outcome: either promoting it to stable or removing
467+
it in a timely manner. Because experimental features can be vulnerable to
468+
security issues, the author is also expected to help assess and patch
469+
vulnerabilities. If an experimental feature has reached mainstream adoption such
470+
that breaking changes are not realistically possible without ecosystem breakage,
471+
it should be considered stable and either be promoted or be removed after a
472+
deprecation cycle.
465473

466474
### Introducing new APIs on the global scope
467475

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.