This is a good question. I'm also interested in the ramifications of
moving baseline labels.
I only move the most recent baseline labels if/when I need to
fix a build error, so I never get burned by it. The baseline is not
yet promoted or used by anyone. I guess it could present a problem
if people are using the baseline and:
- if someone has already checkedout the verison of the file
from which you moved the label. (thus creating a branch
based on the wrong version).
- if a baseline was created on top of this baseline that you
are modifying.
I usually create a new activity in the Integration stream, fix the
build error and move the label. So, the fix activity is not officially
included in the list of activities for that baseline. This doesn't seem
to break interproject merging or rebases. But, I'm always careful to
only modify baselines that are not yet promoted or used by
anyone yet.
I do wonder if I'll ever have a problem with it.
- Maggie
-----Original Message-----
From: KUMAR,KRISHNA (HP-Cupertino,ex3) [mailto:krishna_kumar@hp.com
Sent: Tuesday, July 10, 2001 7:19 PM
To: 'cciug@rational.com'
Subject: [cciug] Can't we change UCM baseline ???
Hi,
I could move the labels (created by baseline) to any version of the element.
When I rebase or create a new stream it picks the correct version what I
wanted
to pick. May be UCM internally has something to do with baseline. But still
I believe
baselines picks the elements looking the labels attached to it.
I believe baselines are in sequential in order baseline1, baseline2, etc....
But it can be managed by moving labels.
Any one knows what are the concerns if I move the labels in baseline ????
(Will it break the system. How ???)
krishna
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 22:03:53 EDT