是否有推广候选版本的规范? [英] Is there any specification for promoting a release candidate?

问题描述

我想知道这一点，因为我刚刚意识到我以前从未参与过提供候选版本的公司，而且我看到这些天这个词被越来越多地使用，所以我想多一点清楚它们的含义.

I'm wondering this because it's just dawned on me that I've never been involved with a company the provided release candidates before and I see the term being used more and more these days so I would like to be a little more clear on their implications.

对于之前曾为提供 RC 的公司工作过的任何人...是否碰巧有任何更正式的规范来说明候选版本的实际含义(例如 RC 和 Beta 之间的区别)，或者是只是每个公司自己决定的政策吗?

For anyone who has actually worked for a company who provides RC's before...does there happen to be any more formal specification for what a release candidate actual entails (like the difference between an RC and a Beta), or is it just a policy thing that each company decides for itself?

如果您碰巧为一家确实有这种规范的公司工作，您能否提供一些示例，说明它所阅读的一些指南确实将版本提升为候选发布版".

If you do happen to work for a company that does have this kind of specification, could you possibly provide some examples of some of the guidelines that it reads do promote a version to 'release candidate'.

推荐答案

我见过 RC 这个词有两种用法:

I've seen the word RC used in two ways:

1. 作为实际的候选版本.这是我们将要运送给客户的版本，除非我们找到一些令人惊叹的东西.在发现主要错误之前不会进行新构建，然后启动新构建并重新开始.通常在发货前存在 3 到 10 个这样的构建版本.
2. 作为优于测试版"的版本.没有实际交付构建的意图，它只是测试版和发布版之间的临时检查点.通常情况下，测试版没有新功能，只有稳定性.这就是 Microsoft 近年来在 Windows 团队(Windows 2000、Windows XP、Windows Vista)中使用该术语的方式.

我自己更喜欢第一个使用.这更有意义.

I prefer the first use myself. It makes much more sense.

这篇关于是否有推广候选版本的规范?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！