-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
Documentation: Stability Indexes #387
Comments
I'm thinking twice about opening this issue. This is not the core node project, so the quotation above shouldn't apply. I think the discussion could go in the wrong direction. This 1.0 release is a really great thing! The release notes are insanely long. A ton of work made this release possible. A ton of work made the whole project possible. I think this release is historic. |
This was referenced Mar 7, 2020
This was referenced Jul 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I know this is probably jumping the gun, as the 1.0 was just released, but I think a lot of people may have this question.
Are the stability indexes in the documentation up to date? The online documentation states 1.0.1 is the current version.
This is significant because 1.0 is supposed to preserve backwards compatibility for ever (see quote). But the following indexes are marked unstable:
Of course, the quote below says "no node 2.0 is not a commitment, but a prediction."
Quoting Isaac Schlueter (this was a while back, 1/2/2012):
The text was updated successfully, but these errors were encountered: