您什么时候应该分支？ [英] When should you branch?

问题描述

在使用SCM系统时，应该何时分支？

When working with a SCM system, when should you branch?

推荐答案

分支有多种用途。最常见的用途之一是分离曾经具有通用代码库的项目。这对于在不影响主干的情况下测试代码非常有用。

There are several uses for branching. One of the most common uses is for separating projects that once had a common code base. This is very useful to experiment with your code, without affecting the main trunk.

通常，您会看到两种分支类型：

In general, you would see two branch types:

• 功能分支：如果某个特定功能具有破坏性，您不希望整个开发团队在早期受到影响，则可以在以下位置创建分支

• Feature Branch: If a particular feature is disruptive enough that you don't want the entire development team to be affected in its early stages, you can create a branch on which to do this work.

Fixes分支：在主干上继续开发时，可以创建一个fixes分支来将修补程序保存到最新发布的版本软件。

Fixes Branch: While development continues on the main trunk, a fixes branch can be created to hold the fixes to the latest released version of the software.

您可能有兴趣查看以下文章，该文章解释了分支的原理以及何时使用它们：

You may be interested in checking out the following article, which explains the principles of branching, and when to use them:

• 内德·巴切尔德-Subversion分支快速入门

• Ned Batchelder - Subversion branching quick start

这篇关于您什么时候应该分支？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！