Manage baselines and releases.

管理基线和发布版本。

Builds baselines for performance tuning.

构建性能调整的基线。

Taking baselines using long-term history data

使用长期历史数据建立基线

Taking baselines using short-term history data.

使用短期历史数据建立基线。

Ability to create and compare project baselines.

创建并比较项目基准的能力。

For taking baselines, focus on report generation.

对于建立基线，主要使用报告生成功能。

G: Maintain consistent baselines for QA reporting.

为 QA 报告维护一致的基线。

Taking baselines using reports on aggregated data.

使用聚合数据报告建立基线。

2 baselines merging into versioned project workspaces.

个基线会合并到版本化的项目工作区。

Create and freeze architecture baselines as workspaces.

创建并冻结结构基线作为工作区。

G: Obtain baselines for more accurate budget forecasting.

为更精确的预算预测获得基线

Baselines are tracked by repository workspaces and streams.

基线可以通过储存库工作区和流来追踪。

Baselines appear as incoming and outgoing, just like change sets do.

正如更改集一样，基准也表现为传入和传出基准。

Additional recommendations for taking baselines on SQL performance.

关于建立SQL性能基线的其他建议。

You can read more about performance baselines later in this article.

本文稍后将会介绍更多有关性能基准测试的内容。

These baselines become the released architectures, or current state.

这些基线会成为发布的结构，或者当前的状态。

A pileup could adversely impact technical, cost, and schedule baselines.

一个连续相撞可能会严重影响技术、成本，以及进度基线。

Baselines and package names should be synchronized to support traceability.

基线和包的名字需要同步以支持可跟踪性。

Add the component baselines (which you just imported), as shown in Figure 9.

添加组件基线(就是您刚刚导入的)，如图9所示。

Mostly it was a lot of blah-blah about baselines and ratios without any numbers.

它的巨大多数篇幅没有任何数字，而是一堆关于基线和比率的无稽之谈。

Release Engineers create Baselines, run Builds, and validate and promote Builds.

释放工程师创建基线、运行构建，以及验证和促进构建。

A Perl script is provided that will "diff" two baselines and populate a baseline record.

一个perl脚本提供两个基线的“差速器”，并构成一个基线记录。

A snapshot is really just a collection of baselines, one for each component in your workspace.

快照实际上就是基准的集合，工作区中的每个组件有一个基准。

These baselines are semantically rich objects that identify a "version" of a UCM component.

这些基线从语义上描述了对象定义的UCM构件版本。

The deployment strategy is to have the software packages named after baselines in ClearCase.

开发策略是在有了ClearCase基线后给软件包命名。

Develop the child Workspace iteratively in this fashion, creating new baselines and versions.

按照这种方式来重复性地开发子工作区，创建新的基线和版本。

Baselines are numbered automatically; as such, specifying a name and description is optional.

基线可以自动编号；就象这样，指定一个名字和描述都是可选择的。

Convert the base ClearCase directory and labels into UCM component directories and baselines.

将Base ClearCase目录和标签转化为ucm组件的目录和基线。

Once created, UCM baselines are immutable and can be used for defining higher-level configurations.

一旦创建，U CM基线是不可变的，并且能用于定义更高级的配置。

The baselines can be used to compare the performance of a DB2 instance during different timeframes.

基线可以用来比较DB 2实例在不同时间段内的性能。