UCM Clear Case:一个项目与多个项目中的流层次 [英] UCM Clear Case: Hiereachy of streams in one project vs multiple projects

问题描述

我们有一个项目，即将向其他稳定的代码库添加新功能，除了修复缺陷外，不会进行任何重大更改.计划不是单独开发新功能一段时间(可能是一个月)进行中间构建和测试，当功能完成并且质量可以接受时，将新功能的代码合并到主分支中.

We have a project and are about to add a new piece of functionality to otherwise stable codebase without any major changes going on except defect fixing. The plan is not develop the new feature separately for a while (probably a month) doing intermediate builds and testing and as the feature is finished and the quality is acceptable merge the code of the new feature in the main branch.

问题是就 Clear Case 而言，以下两种情况中哪一种更好:

The question is what of the following two scenarios is better in terms of Clear Case:

1. 基于当前项目的集成流中的基线创建一个新项目，在这个单独的项目中开发新功能，中间交付到新项目的集成流并从集成流构建.并最终将更改从新项目的集成流交付到主项目(到 dev 或 int).

1. Creating a new project based on a baseline in the integration stream of the current project, developing the new feature in this separate project with intermediate deliveries to the integration stream of the new project and build from the integration stream. And eventually delivering the changes from the integration stream of the new project to the main project (to dev or int).

在主项目中使用流的层次结构:在主项目中创建集成流的子流(我们称之为 temp_int)和 temp_int 的子流(我们称之为 temp_dev).在 temp_dev 中开发新功能，定期传送到 temp_int 并从 temp_int 构建，然后将新功能从 temp_int 传送到主要集成流.

Using a hierarchy of streams in the main project: creating a child stream of the integration stream in the main project (lets call it temp_int) and a child stream of temp_int (lets call it temp_dev). Developing the new feature in temp_dev, with periodic deliveries to temp_int and builds from temp_int and then delivering the new feature from temp_int to the main integration stream.

推荐答案

是否需要创建新项目或制作子流的问题是一个经典问题.

The question whether you need to create a new project or make a sub-stream is a classical one.

在我看来，这两种选择都相当.

In my opinion, both options are fairly equivalent.

唯一显着的区别是您在为此特定开发工作创建新流时可以选择的基础基线:

The only significant difference is the foundation baseline you will be able to pick when creating a new stream for this particular development effort:

• 对于子流，您将只能选择在父流上生成的基线.
• 对于新项目的主流，您将能够选择所需的任何基线.

除此之外:

• 一个新项目为在一个连贯的容器中隔离多个流提供了新的空间.但是，如果您需要包含在新功能开发期间完成的稳定代码的一些小改进，交付将是有序的.
• 子流允许在开发完成后清楚地可视化最终客户端:交付将是合并到父流的自然操作.此外，还可以从父流到您的开发流进行定期变基，以使其保持最新状态.

因此，如果您只有一个需要明确交付的流，那么子流选项就足够了.
如果您的开发最终比预期的更复杂，那么项目会更好.

So if you have only one stream with a clear deliver to make, the sub-stream option is enough.
If your development ends up being more complicated than foreseen, a project is nicer.

这篇关于UCM Clear Case:一个项目与多个项目中的流层次的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！