User1 delivers changes to the integration stream.
用户1向基层流程提交变更。
ClearCase then creates the view for the integration stream.
ClearCase将会为集成流创建视图。
Capturing a project's changes in the enterprise integration stream.
在企业的集成流中获取项目的变更。
Capturing a practitioner's changes in the project's integration stream.
在项目集成流中获取执行者的变更。
Periodically, you will want to rebase your stream from the integration streams.
你可能会阶段性地从集成流变基你的流。
Rational ClearCase creates the new project and the integration stream, as shown below.
RationalClearCase创建了一个新的项目和集成流，如下所示。
Next, the build team USES Rational ClearCase to deliver changes to the integration stream.
下面，构建团队使用RationalClearCase向集成流中交付变更。
When the deliver begins, it creates a special activity to deliver the changes to the integration stream.
当提交开始时，它创建一个特殊的活动提交变更到集成流。
The main stream (PetStore Team Stream) and its various components will flow into the integration stream.
主要流程（PetStore TeamStream）和它的各种组件都将归于这个整合流程。
You have the freedom to deliver that change to the appropriate integration stream when and if you choose.
一旦您选择，您可以自由地将那个变更传递给适当地集成流。
When you create an integration stream and a corresponding UCM project to isolate work targeted at a release.
针对一个具体的发布，何时创建集成流和相应的UCM项目来分散工作。
For the project to build, all internal project streams should flow into what is called an integration stream.
对于这个项目的构建，所有的内部项目流程都应该归于叫做整合流程的流程。
An activity is a development task associated with a stream, in our case, with the ClearCase project's integration stream.
一个活动是一个与流相关的开发任务，在我们的例子中，与ClearCase项目的集成流相关。
saves all changes and checks in all of the checked-out files but does not deliver the development stream to integration stream.
保存所有的变更，并检入所有检出的文件，但是不要向集成流程提交开发流程。
Allowing delivery of only one Unified Change Management (UCM) activity at a time from the development stream to the integration stream.
每次只允许交付一个从开发流程到集成流程的UnifiedChangeManagement (ucm)活动。
The activities are integrated one at a time to an integration stream after which they are built and deployed to appropriate test environments.
这些活动一次集成一个从而形成一个集成流，此后他们被构建并部署到适当的测试环境中。
You can have code merging from the integration stream to your development stream, which involves moving labels and resolving merge conflicts.
你可以从集成流集成代码到开发流，这包括移动标签并解决合并冲突。
More complex projects might have one or more levels of development streams originating from various baseline configurations of the integration stream.
更复杂的项目可能有一个和更多级别的开发流，它们始于集成流的不同基线配置。
Note: An integration stream's default recommended baselines are its foundation baselines. A development stream has no default recommended baselines.
注：一个集成流的默认推荐基线是其基础基线。一个开发流没有默认推荐基线。
When delivering activities, the change set (s) attached to the activities are delivered to the integration stream so that everyone on the team can see the changes.
当提交活动时，变更集关联到这些提交到集成流里的活动，因此团队里的每个人能看到这些变更。
That developers are always able to successfully merge and commit their changes in the integration stream without being affected by deliveries from other developers.
开发人员总能够成功地合并并在集成流中提交他们的变化，而不被其他开发人员的交付所影响。
Once testing is complete, he checks the code back into IBM Rational ClearCase and delivers the changes to an integration stream, again without needing to leave his IDE.
一旦测试完成，他将代码检入回IBMRationalClearCase，并且向一个集成流中交付这个更改而不需要离开他的IDE。
Once you have finished working on an activity, you can deliver your changes to the default integration stream (parent stream), or to any other stream that you choose.
一旦在一个活动上结束工作，你可以提交你的变更到默认的集成流(父流)，或者提交到任何其它的你选择的流。
The model and fragments will be merged silently in integration stream because the changes are trivial, given that User1 is the first to deliver changes to the stream.
模型和片段将会在集成流程中静静的得到合并，因为变更是平凡的，毕竟用户1是第一个向流程提交变更的。
Teams are free to choose how many sub-feature streams they need, if any, and they are also free to choose how often they want to deliver their changes to an integration stream.
团队可以自由选择他们需要多少的子特性流，如果有够多的流的话，同时它们也可以自由选择多久向集成的流，交付他们的变更。
If you start working with ClearCase, the integration stream going forward will be created from the baseline (created as a result of importing the label), as shown in Figure 10.
如果您从ClearCase开始，那么集成流会从基线创建(作为导入标签的结果创建)，如图10所示。
Figure 1: File changes are based on activities, which are integrated one at a time to an integration stream, after which they are built and deployed to appropriate test environments.
图1：基于活动的文件变更，这些活动一次集成一个集成流，此后他们被构建并部署到适当的测试环境中。
Which means, if you deliver more than 1 activity from development stream to integration stream in one go, there will still be single delivery activity created on the integration stream.
这意味着，如果您从开发流程交付了不止一个活动到集成流程，那么对于集成流程都会创建单独的交付活动。
This would increase the reliability of the code that is checked in and empower developers to have confidence that the work they are committing to the integration stream will work downstream.
这样做将增强代码的可靠性，并且使得开发人员对于他们提交给综合流的工作更加具有信心。
In ClearCase terms, the agile project's build process is set to monitor the integration branch (or UCM stream) and then execute a build script on check-in.
在clearcase术语中，敏捷项目构建过程用于监控集成分支(或ucm流)以及在检入时执行构建教本。
应用推荐