是否应发布“候选候选人"?是一成不变的? [英] Should a "Release Candidate" be immutable?

问题描述

如果我们有一个用于停止功能和进行错误测试的源代码控制分支(包括在该分支上的其他提交以修复所述错误)，应该怎么称呼它?

If we have a source control branch that we use to stop features and bug test (including additional commits on this branch to fix said bugs), what should it be called?

候选候选人"合适吗?

我的想法是，这样的分支将被称为发布"，并且使用候选"一词意味着它是不可变的.您可以有候选项1和候选项2，但是这些特定的候选项永远都不会改变. IE.候选人1没有任何提交，将以任何方式对其进行修改.

My thoughts are that such a branch would be called "Release" and that using the word "candidate" implies it is immutable. You can have candidate 1 and candidate 2, but those specific candidates should never change; ie. candidate 1 wouldn't have any commits, that would modify it in any way.

链接或示例将非常有用，因为我与之讨论的人都非常头脑清醒.

Links or examples would be great, as the person I was discussing this with is very hard headed.

相关问题:有关促进发布的规范吗?候选人?(介绍如何考虑完成的RC)

Related question: Is there any specification for promoting a release candidate? (covers how finished RC can be considered)

推荐答案

仍然可以将其视为最终的集成步骤(在这种情况下，不是一成不变的"):

It can still be considered as a final integration step (and in that, "not immutable"):

您仍然在这里:

• 集成了批准用于下一版本的功能.
• 修复在集成测试(SIT-系统集成测试和UAT，用户验收测试)后出现的错误

您可以认为"RC"更加稳定 ，但您仍然可以修复显示阻止程序错误.
从这个意义上讲，您将不会同时拥有候选人1"和候选人2". RC通常是顺序.

You can consider "RC" as being even more stable that I just described, but you could still fix show-stopper bugs.
In that sense, you wouldn't have "candidate 1" and "candidate 2" (simultaneously). RCs are usually sequential.

然后，发布"分支用于后期制作(热修复和版本维护).
它将在进入生产阶段时冻结应用程序的状态，并在开始时使用该状态来保持生产状态.

Then, a "Release" branch is for post-production (hot-fixes, and release maintenance).
It freezes the sate of the application when going into production, and uses that at a starting point to maintain what is into production.

简而言之:

• 分支不是一成不变的:它们隔离了开发开发生命周期中的努力.
  应该期望您添加提交.在任何分支机构中.
• 标记(或标签"或基准"或...)是不可变的:它们会在某个时间点冻结​​代码的特定状态

• branches aren't immutable: they isolate a development effort in the development lifecycle.
  You should be expected to add commits. In any branch.
• Tags (or "label", or "baseline", or...) are immutable: they freeze a specific state of the code at a point in time.

这篇关于是否应发布“候选候选人"?是一成不变的?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！