Alpha release version confusion - Information required
维护者通常 3 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 45/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 领域
- documentation, release
调研方向
The question is about which release tag to use, so start with the README and any docs or CHANGELOG in the repository, then check the GitHub releases page for v2.0.0-alpha-2 and v2.0.0-alpha-3. Confirm with a maintainer whether alpha builds are pre-releases and whether v2.0.0 is planned, since the answer is a policy decision. Done means a short documented explanation of what the alpha tags are and which one to pick.
由索引模型根据 Issue 内容生成。
描述
Hi there,
Now that there are two releases by name v2.0.0-alpha-3 & v2.0.0-alpha-2, we are confused if we have to pick up v2.0.0-alpha-3 which has been tagged as latest or wait for the upcoming v2.0.0 major version itself. I could not find any information as to what these alpha versions are, and if they are a kind of pre-release versions.
Any inputs regarding this would have been helpful.
Thanks in advance.
- 主要语言
- Go
- 星标
- 234
- 派生
- 265
- 平均合并
- 2 天 12 小时
- 30 天内合并 PR
- 21
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
相似的 Issue
-
meta
难度 2/5 1-3 小时 新手友好度 62/100
last9/last9-mcp-server#554 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 85/100
-
NodeOpUpgrade copies Pod resolv.conf into host OS, causing CoreDNS loops and image-pull failures未关闭area/operator bug chore
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 86/100
DNSCrypt/dnscrypt-resolvers#1107 ·
-
backend in-progress task
难度 1/5 1 小时以内 新手友好度 90/100
jphacks/kz_2601#2101 · 1 条评论 ·
维护者通常 1 天内回复