Caveat: I know (almost) nothing about RTC& Jazz.

Our new group is considering standing up RTC, and will need to do
something like the following:

Connect Synchronizer to main/latest on a remote CC server
("A") in order to propagate changes from A into a branch
("B") that is sitting inside our new local RTC server. We
would then selectively choose changed files in B to propagate into a
working RTC branch ("C"). So, A is the remote CC main /
latest; B is our local mirror of A, and C is our current release
working branch.

Here's the question: if we do all this, will the change history,
including comments, who changed, etc., of changes made in A make it
all the way to C for file changes we choose to propagate from B in to
C?

Thanks in advance!

Thanks, Geoff. Would it be possible to configure the Synchronizer to
propagate all changes from CC main/latest so that there are no
versions that are missed? If we did this, would we see all CC changes
& their comments in the "mirror" copy in RTC?

gmclemmwrote:
No, only very limited meta-data is transferred by the synchronizer
(in
particular, the list of UCM activity ID's, if you are using UCM).
You
can request that the comment be brought over, but that will just be
the
comment on the most recent version in ClearCase, not the comments on
all
the versions between the version last sync'ed and the version
currently
sync'ed. To find that detailed change history information, you
would
have to go back to the original repository where the change was made
(in
this example, ClearCase).

Cheers,
Geoff