将 SVN 设置为 Best Suit Dev ->质量检查 ->产品 [英] Setting up SVN to Best Suit Dev -> QA -> Prod

问题描述

如果有人问过这个问题，我很抱歉，但我无法找到针对这种情况的具体答案:

I'm sorry if this has already been asked, but I haven't been able to find an answer specific to this situation:

对于我们的 Web 应用程序，我们有 3 个系统:开发、质量检查和生产.目前，第三方正在维护代码，但很快就会掌握在我们手中.我们将为每个阶段提供单独的构建环境.此外，我们使用 RAD 进行代码开发，因此实际上会有一个主要步骤，测试/沙盒.

For our web application, we have 3 systems: dev, QA, and production. Right now, a third party is maintaining the code, but soon it will be in our hands. We will have separate build environments for each stage. Also, we use RAD for code development, so there'll actually be a primary step, test/sandbox.

理想情况下，我们希望以某种方式隔离每个阶段的存储库，以便我们从 DEV 检出，进行一些更改，在本地测试它们，然后将它们检回 DEV.如果 Dev 一切正常，我们将检查 QA，等等.

Ideally, we'd like to somehow isolate repositories for each stage, such that we check out from DEV, make some changes, test them locally, and check them back into DEV. If everything is ok on Dev, we will check into QA, and so on.

我们是否应该为每个存储库提供单独的存储库，或者这是否属于分支"，在那里我们将为开发、质量检查和生产创建一个单独的分支.您能否还提供实现理想路线的最佳方法?

Should we have separate repositories for each, or would this fall under 'branching', where we'd have a separate branch for dev, QA, and prod. Could you also provide the best means of implementing whatever the ideal route is?

如果还有其他问题，请告诉我.

Let me know if there are any other questions, also.

谢谢克里斯

推荐答案

使用分支和合并

我们执行以下操作:

当我们发布时，我们会创建一个当前发布分支.我们在不同版本之间修复错误，然后将它们合并回我们的主干.

When we release we create a current release branch. We make bug fixes here between releases, then merge them back to our trunk.

我们在主干上开发，当我们准备发布时，我们会创建一个 QA 分支.我们对其进行测试和修复，然后将其推出，它成为我们当前的发布分支.

We develop on trunk and when we are ready to release we make a QA branch. We test and fix on it and then push it out and it becomes our current release branch.

这篇关于将 SVN 设置为 Best Suit Dev ->质量检查 ->产品的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！