Confusion regarding “Maintenance LTS” status
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 文档
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- node.js
- 领域
- documentation, release
调研方向
首先审查现有的 Maintenance LTS 术语以及 issue 中包含八条评论的讨论，包括措辞变更的历史。项目就如何以更清晰的语言为库和应用开发者提供有关此阶段迁移和支持的指导达成一致，即为完成。
由索引模型根据 Issue 内容生成。
描述
I’ve been reading through the history a bit of how “Maintenance” was changed to “Maintenance LTS.” There seems to be good reasoning behind the wording but what I’m finding is that there are some unintended consequences that need to be resolved.
In my view, maintenance means “get off of this.” In fact, it’s my view that it needs to mean that, especially for libraries since they have to move people early in order to push applications to upgrade before the window closes. The end of maintenance means “no more security fixes.” It means “when this is over it’s potentially harmful to run this version.” But that’s not the way people are interpreting it.
Library authors seem to think that they should ensure support in the most recent versions of their libraries until the end of this window. I don’t think that’s the intention, because we need the ecosystem to be migrating away from this version during that maintenance window if we ever hope to have applications and vendors migrated off before the window closes. There’s a limited number of incentives Node.js has to push an ecosystem this large and complex in a more secure direction, and the current wording and lack of clear direction to developers means the few incentives we have aren’t being used very effectively.
It might be worth changing the language here to clarify the desired behavior of library and application developers and potentially re-wording some of these terms.
- 主要语言
- JavaScript
- 星标
- 4.4k
- 派生
- 675
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
nodejs/Release 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 88/100
-
Release-agenda
难度 1/5 1-3 小时 新手友好度 78/100
-
CitGM backlog未关闭
难度 4/5 3-5 天 新手友好度 50/100
-
难度 1/5 1 小时以内 新手友好度 20/100
-
难度 1/5 1 小时以内 新手友好度 35/100
相似的 Issue
-
feature task
难度 2/5 1-3 小时 新手友好度 72/100
RealDevSquad/website-www#1178 ·
-
难度 2/5 1-3 小时 新手友好度 68/100
netlify-labs/nax#56 · 2 条评论 · 1 个 reaction ·
-
accessibility bug revealjs
难度 2/5 1-3 小时 新手友好度 84/100
quarto-dev/quarto-cli#14961 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
PnX-SI/GeoNature#4435 · 2 条评论 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 85/100
openlayers/openlayers#17648 ·
维护者通常 1 天内回复