[DOCS] EOL Policy

未关闭
  • 哪里不对？
#28 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
42/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
停滞
领域
documentation

调研方向

Start by reviewing hardware-software.md and the support page linked in the issue to see how requirements, versioning, and changelogs are currently documented. Write an explicit EOL policy guide from the policy details in the issue, and consider whether a support matrix is needed. Done means the guide clearly documents deprecation notice, fixes, breaking changes, connector support, and manual support timelines.

由索引模型根据 Issue 内容生成。

描述

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:

Graphistry EOL policy is:

  • API deprecation:
    -- 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
  • Fixes go into new versions (vs. LTS patching)
  • Document breaking changes in the release changelog, as well as significant internal infra upgrades
  • 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)
  • Manual support: 2yr old version for enterprise, 1yr old for cloud
主要语言
Shell
星标
31
派生
6
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

graphistry/graphistry-cli 的其他 Issue

查看 graphistry/graphistry-cli 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。