-
Notifications
You must be signed in to change notification settings - Fork 5
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
[DOCS] EOL Policy #28
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should have an explicit EOL policy guide and, potentially, an explicit support matrix. We can then move version numbers out of other docs.
Currently available:
Software reqs, including supporting minimums: https://github.com/graphistry/graphistry-cli/blob/master/hardware-software.md
Support, including links to changelogs & versioning: https://www.graphistry.com/support
Graphistry EOL policy is:
-- Avoid most deprecations by making new APIs additive vs. breaking
-- Aim for 1+ year notification window when unavoidable
-- Ex: We still support our 1.0 REST protocol, and are only now moving to officially deprecate it
The text was updated successfully, but these errors were encountered: