doc: clarify release candidate stability index #59295
Open
+3
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aduh95
approved these changes
Jul 31, 2025
|
@nodejs/next-10 Not sure where would be the correct place to ask, but it'd be interesting next time we do a survey to ask whether the ecosystem uses the different experimental stages |
panva
added
the
author ready
jasnell
approved these changes
Jul 31, 2025
panva
added
the
commit-queue
RafaelGSS
approved these changes
Jul 31, 2025
JakobJingleheimer
approved these changes
Jul 31, 2025
targos
approved these changes
Jul 31, 2025
You can start an issue in the next10 repo, where we can gather suggestions for 2026 survey |
ruyadorno
approved these changes
Jul 31, 2025
lpinca
approved these changes
Jul 31, 2025
BethGriggs
approved these changes
Aug 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the Experimental
1.2 - Release candidatestability index to indicate that changes may occur not only because of user feedback but also, in some cases, due to the underlying specification late development changes.I wish to be able to mark upcoming Web Cryptography additions 1.1 - Active development with runtime experimental warning but when the dust around the WICG spec settles I wish to remove the experimental warning and mark them as 1.2 - Release candidate.
However, given past experience it may take a long time before the features get merged into the main Web Cryptography spec and in those cases I wish to reserve the option to reflect last minute changes to the spec in the implementation.
cc @nodejs/tsc