如何处理git-flow中的释放候选人
我们正在 git-flow 工作流程。通常，我们在运送最终版本（v1.0.0）之前发布了一些释放候选者（RC，v1.0.0-rc.0）。
为此，我们有一个版本分支（Release/1.0.0）。该分支中的发布候选者只是标签。在我们有最终版本之前，不会将发行分支合并到main中。
今天，我们讨论了是否应该为每个发行候选者打开 （例如repares/1.0.0-rc.0），并在候选人发布时将其合并到MAIN中。
对此有任何意见吗？
We're working by the git-flow workflow. Typically we release some release candidates (RC, v1.0.0-rc.0) before we ship the final release (v1.0.0).
To do so, we have a release branch (release/1.0.0). The release candidates are just tags within that branch. The release branch is not merged into main until we have a final release.
Today we discussed whether we should open a release branch for every release candidate (e.g. `release/1.0.0-rc.0) and merge these into main whenever the candidate is released.
Any opinions on this one?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
通常，如果以前的每个候选者都是最新的候选者访问，则可以在同一分支上，因此每个分支机构都没有任何好处。
如果您想制作一个不从当前发行候选人开始的新版本候选人（例如，您需要备份一些提交，甚至重新开始），那将是考虑创建新分支机构的好时机。
我假设，一旦您合并到
main中，您都可以删除所有发布分支，无论它们是否已完全合并到main中。由于您仍然有未使用的旧版本版本，因此即使没有分支机构，也可以随时回到他们身边。Generally, if each of the previous release candidates are reachable by the newest one, then they could be on the same branch, and therefore there isn't any benefit to having separate branches for each.
If you wish to make a new release candidate that does not start from the current release candidate (e.g. perhaps you need to back up a few commits, or even start over), then that would be a good time to consider creating a new branch.
I assume once you merge into
mainyou can delete all of the release branches, whether they were fully merged intomainor not. Since you still have the old release versions tagged that you didn't use, you could always go back to them if you wish, even without the branches.