UCM ClearCase中基准线/基准线策略的生命周期 [英] Life Cycle of Base Line/ Base line strategies in UCM ClearCase
问题描述
我们提出了一种流策略，该策略具有一个主要的集成流以及用于其他环境的其他几个流。如下所示。
We have come up with a stream strategy which has a main integration stream and several other streams for the other environments. A brief idea as shown below.
Integration Stream
-- Production
-- Development
---- Stream for release 1.0
---- Stream fix release 1.0
我们打算将子流用于开发，并将其交付给开发流，然后选择活动并创建基线并将其提升到集成流。
We intend to use the child streams for development and deliver it to the Development stream and choose the activities and create a baseline and promote them to the integration stream.
我读过几本书论坛上内容丰富的帖子，我毫不怀疑。我是UCM环境的新手，发现很难全面了解用法。
I read couple of highly informative posts on this forum and I have few doubts to begin with. I am new to the UCM environment and finding it tough to get the broader picture of the usage.
- 是否应在开发中创建基准分支或集成分支。
- 基线如何贯穿生命周期？
我们在测试，发布后创建的基准是否仅更改促销级别？
如果任何人都可以描述这个过程。
It would be very helpful if anyone could describe this process.
预先感谢。
致谢
推荐答案
1 /应该在开发分支或集成分支上创建基线。
1/ Should the baselines be created on the development branch or the integration branch.
您可以在任何所需的流上创建基准。它们只是可写组件上的标签。
如果需要清理它们，可以稍后将中间基准废弃（使其处于锁定状态和不可见状态）。
You can create a baseline on any stream you want. They are just labels on the writable components.
Intermediate baselines can later be "obsoleted" (made locked and invisible) if you need to clean them up.
您的开发流应重命名为合并，因为在这里您将合并实际用于生产的内容（并在集成流中交付：此处不需要生产流）。
Your Development stream should be renamed into "Consolidation", because this is where you will consolidate what will actually go to Production (and delivered on "Integration Stream": your "Production" Stream is not needed here).
由于修复将从正式（即生产中）标签开始，因此我建议将流 Stream fix release xy移到Integration Stream下方
Since the fixes will begin from an "official" (i.e. "in production") label, I would recommend moving the stream "Stream fix release x.y" below the Integration Stream
注意：您需要注意交付活动 创建一个时间轴，以链接所有源流中的活动。这意味着您可以将部分活动从流A传递到流B，但不能从流A传递到流C（除非您传递 all 活动）。
简而言之，为 all 活动提供基准和交付总是比较简单。
Note: you need to be aware that a "deliver activities" creates a timeline linking all the activities from the source stream. That means you can deliver a partial set of activities from stream A to stream B, but you won't be able to deliver from stream A to stream C (unless you deliver all activities).
In short, baselining and delivering all activities is always simpler.
2 /基线贯穿生命周期
2/ How does the baseline goes through the life cycle
首先，状态 TESTED， VALIDATED，...仅仅是元属性您可以将其设置为所需的任何值，而与设置基线的流没有任何关系。
First, the status "TESTED", "VALIDATED", ... is just a meta-attribute you can set to whatever value you want, without any relation with the stream where the baseline has been set.
然后，生命周期取决于：
The life-cycle is then determined by:
- 合并的工作流使您能够将不同的开发工作从一个分支（从流构建）转移到另一个分支。
- 您与基准关联的状态（元数据）。
这篇关于UCM ClearCase中基准线/基准线策略的生命周期的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
