Hi all,

What would be the best practice to label a Baseline State?

Let me explain: My Build Engine just created a new successful build
(it also created a Snapshot for the components that were loaded in
the RTC WS that was assigned to that Build Definition).
I can decide to follow up the Promotion path were I'd share that
Generic Snapshot back to the Integration Stream, but this is not
enough.
I'd like to be able to manage this baseline state.
For example When the SIT was completed by the QA team, I'd like to
flag it as SIT_PASSED
Once we deploy the code related to that snapshot to UAT environment
and the UAT has passed I'd like to flag it as UAT_PASSED.
Off course once deplyed in production it has to be flagged as
PRODUCTION.
Previously in Rational ClearCase, we had the ability to promote a
Baseline (different promotion concept than the one used in RTC) and
we were also able to filter the baselines according to their
promotion status.
So I was able to re-create a Stream with the last version (or
baselines) of the components that were tagged as deployed in
production (with the Attribute PRODUCTION).
Is there a way or a good methodology that we could follow in RTC in
order to realize the same goal?
Right now by renaming the snapshots from 20101010_1306 to
PROD_201010_1306 for each component was the only way I found so far
to adapt the ClearCase Baseline promotion mechanism.
I don't like that way since I rename something that is supposed to
stay static.
I also don't feel confortable to create a new Baseline that points on
the same state of the code, since even if it is supposed to be in the
same state, it still not the baseline that was created by my
successful build.

Please share with us your thoughts on the question.
Take care all!

I recommend that you represent the "state" ("promotion level") for a
baseline in the form of an RTC stream. To mark a baseline as being at a
given promotion level, just deliver it to the stream for that promotion
level. One of the advantages of this approach is that you can see the
"history" of that promotion level, i.e. the sequence of baselines that
have achieved that promotion level.

Cheers,
Geoff

This solution doesn't look to scale as we have 18 Streams& DEV,
QA, UAT, PROD as states would make it 72 Streams. In addition we will
have bug fix streams.

I recommend that you represent the "state"
("promotion level") for a
baseline in the form of an RTC stream. To mark a baseline as being
at a
given promotion level, just deliver it to the stream for that
promotion
level. One of the advantages of this approach is that you can see
the
"history" of that promotion level, i.e. the sequence of
baselines that
have achieved that promotion level.

Cheers,
Geoff