In RTC, you would normally define a stream for each promotion level,
such as the "release-1.2" stream. To promote a snapshot to the release
stream, you would then deliver the configuration to be promoted to the
release-1.2 stream, and then create a snapshot of the release-1.2 stream.

Alternatively, instead of delivering the configuration to the
release-1.2 stream, you could just create the snapshot wherever you
wanted, and then change the owner of the snapshot to be the release-1.2
stream.

Then to retrieve the snapshot to a working location, just create a new
repository workspace from that snapshot.

Cheers,
Geoff

On 10/5/2011 7:23 AM, jensene wrote:

We are looking at moving this to a Team Concert repository but need to
get a few answers on how to migrate our current build process.

We currently have a ClearCase repository following a main line
pattern.

Baselines created on the mainline have their promotion level changed
to RELEASED once/if they are deployed to production.

As part of our application build we need to produce a delta of all the
new/changed SQLJ files between the current baseline and the last
production baseline.

Is there a similar method in Team Concert for marking a snapshot as
RELEASED? Can we then retrieve the snapshot to a working location?