Commit 40a4337
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
1 file changed
Lines changed: 8 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -462,6 +462,14 @@ For pull requests introducing new core modules: | |||
| 462 | 462 | * Land only after sign-off from at least two TSC voting members. | |
| 463 | 463 | * Land with a [Stability Index][] of Experimental. The module must remain | |
| 464 | 464 | 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. | ||
| 465 | 473 | ||
| 466 | 474 | ### Introducing new APIs on the global scope | |
| 467 | 475 | ||
0 commit comments