[英]Merging feature branches to release branch instead of trunk
I have a question about two source control scenarios, both with feature branches and release branches: 我对两个具有功能分支和发布分支的源代码控制方案有疑问:
What are the consequences of scenario 2 compared to scenario 1? 与方案1相比,方案2的后果是什么?
What are the possible advantages and disadvantages of both scenarios? 这两种情况的可能优点和缺点是什么?
More details of the two scenarios: 两种情况的更多详细信息:
Scenario 1 (similar to what is described in this SO-answer ): 场景1(类似于此SO-answer中描述的场景):
Scenario 2: 方案2:
Since branching is all about isolation (see " When should you branch ), the difference between the 2 scenarios is the role you want the main branch trunk
to have : 由于分支完全是关于隔离的 (请参阅“ 何时分支” ),因此两种方案之间的区别是希望主分支
trunk
具有以下角色 :
Scenario 2 is more adapted to a static role : trunk
would be the representation of what is in production (and the occasional hot-fixes needed to be merge back to current feature and next-release branch) 方案2更适合静态角色 :
trunk
将表示生产中的产品(偶尔需要将修补程序合并回当前功能和下一发行版分支)
Scenario 1 is more suited for a dynamic role : trunk
is the integration for various feature, release branches being made from there to consolidate the features which will actually be part of the next release. 场景1更适合于动态角色 :
trunk
是各种功能的集成,从那里创建了发布分支以合并功能,这些功能实际上将成为下一版本的一部分。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.