An understanding of how certain Rational Team Concert™ source
control concepts
relate to similar ones in Rational® ClearCase® can
help Rational ClearCase users
adapt to using Rational Team Concert source
control.
For a concise overview of Jazz™ terminology and concepts, see
the Quick reference or
the Overview of Rational Team Concert source control.
- In Jazz, a version-controlled file or folder is
called a "versionable item," which is analogous to an element in a
VOB.
- A versionable item is modified in the context of a "repository
workspace," which is analogous to a UCM development stream or a base Rational ClearCase private
branch. Changes you make in a repository workspace are private to
that workspace until you deliver them.
- A projection of a repository workspace onto the local file system
is called a local workspace. A local workspace is analogous to a Rational ClearCase view.
If you are using the Eclipse client, the local workspace is an Eclipse
workspace. Any file or folder in the local workspace can be modified,
so there is no explicit checkout operation. This behavior is similar
to the auto-checkout behavior provided by existing Rational ClearCase plug-ins
for Eclipse. When you check in a file or folder, it is assigned to
a change set, which is analogous to the change set of a UCM activity.
- A Jazz stream tracks the history of a collection
of "versionable items," and is analogous to a UCM integration stream.
- When you are ready to make changes you have made in a workspace
available to other team members, you deliver them to a stream, just
as when changes made in a UCM development stream are ready to be seen
by other team members, you deliver them to a UCM integration stream.
- When you want to record a particular configuration of a workspace
or stream, you create a "baseline" in that workspace or stream, just
as you create a UCM baseline in a UCM development or integration stream.
Unlike a UCM baseline, which is fixed to the stream in which it is
created, a Jazz baseline can be delivered from a workspace
to a stream.
- When you are ready to see the changes that have been delivered
to a stream, you accept those changes into your workspace. This is
analogous to rebasing a UCM development stream to see the changes
that have been delivered to a UCM integration stream. The accept operation
lets you accept all the changes from the stream, or a selected baseline
from a stream, just as the UCM rebase operation lets you specify the
latest configuration of the UCM integration stream, or a selected
UCM baseline of the UCM integration stream.
- An accept operation can introduce conflicts, just as a UCM rebase
can introduce conflicts. Rational Team Concert source
control provides
merge tooling to help resolve these conflicts.
- A work item specifies issues to be addressed (for example, product
enhancement or defect-fixing requests), and is analogous to a ClearQuest-enabled
UCM activity. In particular, like a ClearQuest-enabled UCM activity,
a work item allows you to associate a change set with a particular
enhancement or defect fix, and to track that change set as it flows
through the overall development effort.
- A project area defines a process and set of policies that apply
to all streams and work items in the project area, and is analogous
to a UCM project with its project policies.