Regarding Replacing the components from local workspace OR different Stream and it's impact on the resulted change sets
![]() Let's say , I have two streams , Stream A and Stream B , both using same Component C and there are numbers of Developers working on these streams.
|
Accepted answer
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Sep 11 '17, 4:08 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
There are two distinct operations: "Replace" and "Accept/Deliver".
- "Replace" of a configuration X of a component in a stream/workspace with another configuration Y of that component effectively discards whatever change sets are currently in configuration X, and replaces them with the change sets of the configuration Y. It doesn't matter whether configuration Y is a baseline or is from another workspace/stream, and it doesn't matter whether configuration X is in a workspace or stream ... the semantics of replace is always the same.
- "Accept/Deliver" of configuration Y of a component to a configuration X of that component in a stream/workspace effectively adds all change sets in Y that are not already in configuration X to configuration X (so it is like a "union" operation). It doesn't matter whether the source configuration is a baseline or is from a stream/workspace, and it doesn't matter whether the target configuration is in a stream or a workspace ... the semantics of accept/deliver is always the same.
Note that there are statements in the question that are ambiguous/unclear.
- When you said "create a baseline of his current workspace", I'm assuming you meant "create a baseline of component C in his repository workspace" (one can create a snapshot of a workspace, not a baseline).
- What does "post that accepted all Incoming Change sets into his local Workspace" mean?
I assume by "his local Workspace", you just meant "his workspace" (if not, please explain).
I also assume that by "post that accepted", you just mean "accepted" (if not, please explain).
I am assuming that the 10 change sets are in addition to the change sets of Component C that were already in the workspace (in which case, the history after the accept is something like <32, 33, 34, 1, 2, 3, ..., 9, 10>).
Just for interest's sake, why mention Developer B and Stream B, if they are not relevant to your questions?
Amit Kumar selected this answer as the correct answer
Comments 1 . Yes, I meant "create a baseline of component C in his repository workspace". Sorry for the confusion.2. Yes. "his workspace".3. Yes, "accepted"
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.