René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[DOCS] EOL Policy","articleBody":"We should have an explicit EOL policy guide and, potentially, an explicit support matrix. We can then move version numbers out of other docs.\r\n\r\nCurrently available:\r\n\r\n* Software reqs, including supporting minimums: https://github.com/graphistry/graphistry-cli/blob/master/hardware-software.md\r\n\r\n* Support, including links to changelogs \u0026 versioning: https://www.graphistry.com/support\r\n\r\nGraphistry EOL policy is:\r\n\r\n* API deprecation: \r\n-- Avoid most deprecations by making new APIs additive vs. breaking\r\n-- Aim for 1+ year notification window when unavoidable\r\n-- Ex: We still support our 1.0 REST protocol, and are only now moving to officially deprecate it\r\n* Fixes go into new versions (vs. LTS patching)\r\n* Document breaking changes in the release changelog, as well as significant internal infra upgrades\r\n* Connectors: Latest major version of a product; we will be revisiting in Q2/Q3 for supporting multi-major-versions (e.g., we support both Neo4j 3 + Neo4j 4)\r\n* Manual support: 2yr old version for enterprise, 1yr old for cloud","author":{"url":"https://github.com/lmeyerov","@type":"Person","name":"lmeyerov"},"datePublished":"2021-01-26T18:23:57.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/28/graphistry-cli/issues/28"}