Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: add experimental stages #46100

Merged
merged 3 commits into from
Jan 14, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 15 additions & 3 deletions doc/api/documentation.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,18 @@ The stability indices are as follows:
> [semantic versioning][] rules. Non-backward compatible changes or removal may
> occur in any future release. Use of the feature is not recommended in
> production environments.
>
> Experimental features are subdivided into stages:
>
> * 1.0 - Early development. Experimental features at this stage are unfinished
GeoffreyBooth marked this conversation as resolved.
Show resolved Hide resolved
> and subject to substantial change.
targos marked this conversation as resolved.
Show resolved Hide resolved
> * 1.1 - Active development. Experimental features at this stage are nearing
GeoffreyBooth marked this conversation as resolved.
Show resolved Hide resolved
GeoffreyBooth marked this conversation as resolved.
Show resolved Hide resolved
> minimum viability.
RaisinTen marked this conversation as resolved.
Show resolved Hide resolved
> * 1.2 - Release candidate. Experimental features at this stage are hopefully
GeoffreyBooth marked this conversation as resolved.
Show resolved Hide resolved
> ready to become stable. No further breaking changes are anticipated but may
> still occur in response to user feedback. We encourage user testing and
> feedback so that we can know that this feature is ready to be marked as
> stable.

<!-- separator -->

Expand All @@ -48,9 +60,9 @@ Features are marked as legacy rather than being deprecated if their use does no
harm, and they are widely relied upon within the npm ecosystem. Bugs found in
legacy features are unlikely to be fixed.

Use caution when making use of Experimental features, particularly within
modules. Users may not be aware that experimental features are being used.
Bugs or behavior changes may surprise users when Experimental API
Use caution when making use of Experimental features, particularly when
authoring libraries. Users may not be aware that experimental features are being
used. Bugs or behavior changes may surprise users when Experimental API
modifications occur. To avoid surprises, use of an Experimental feature may need
a command-line flag. Experimental features may also emit a [warning][].

Expand Down