Evaluate automated github release policy

已关闭
#1,432 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
cpp, github
领域
release

调研方向

Start by reviewing the repository’s automated GitHub release workflow and how it relates to stable releases on haxelib; the issue does not name specific files or tests. Decide whether to stop automatic releases or mark them with unstable version numbers and preview status, and consider how to identify the commit required for Haxe 5.0.0-preview.1. Done means the release policy is clear and the selected behavior is implemented.

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

描述

I wonder sometimes whether it is actually that useful to have a github release on every commit. It might give a false impression that these are stable releases, which they are not, and things can break and change between commits. It also creates noise, and makes it harder to find actual stable releases. It is also confusing that they are on github, but not on haxelib.

Maybe we should turn off these automated releases, or at least give them explicit unstable version numbers (like 4.3.x-alpha.y or something) and mark them as preview releases.

(as an aside, it would also be useful if it was easier to identify a428509569b8fa251f2317aa0fe9ed2de1927980 (aka v4.3.91) as the version required for haxe 5.0.0-preview.1)

主要语言
C++
星标
330
派生
233
平均合并
10 小时 49 分钟
30 天内合并 PR
19

环境准备

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

从这里开始

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

HaxeFoundation/hxcpp 的其他 Issue

查看 HaxeFoundation/hxcpp 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

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