Moving change-set across streams
How can the change set be moved across Streams ?
For example : Two developers working on two streams but on same component. There is a need for a takeover of particular change-set.
Stream 1 workspace working on abc.xml file:
|
Baseline created
|
change-set 1
|
change-set 2
Stream 2 workspace working on same abc.xml file:
|
Baseline
|
change-set 3
|
change-set 4
If changes-set 1 need to be moved to Workspace of Stream 2.. How this scenario can be achieved ?
2 answers
1. The fundamental way how RTC SCM works is: For the stream configuration you want the change set to be in, create a repository workspace. Follow the answer to your question https://jazz.net/forum/questions/261615/how-movement-of-changeset-to-another-repositary-workspace-done to accept the change set into your repository workspace and then deliver the change to the stream.
- https://jazz.net/library/article/1439 provides more options
- https://jazz.net/library/article/1481 is about best practices and basics that should be known as well
2. Fix your language, you are not moving anything. You make a change to be included in different contexts.
3. Consider basic training. http://www.islandtraining.com/ is a partner that has great RTC/CLM trainings. You want to do a train the trainers model where you train some people the tool usage and allow them to become knowledgeable. These people build the pool of experts that help other users to get started.
This question is similar to the one you asked in https://jazz.net/forum/questions/261615/how-movement-of-changeset-to-another-repositary-workspace-done
Another way to do this is:
a) The first developer sets the flow target of Stream1_Workspace to Stream2 and delivers change sets 1 & 2 to Stream2. The second developer accepts the change sets and merges the changes.
Comments
All the 3 ways mentioned in https://jazz.net/forum/questions/261615/how-movement-of-changeset-to-another-repositary-workspace-done works perfectly fine between repository workspace. But change-set takeover across streams don't really need above options.
For e.g. If a flow connection is established b/w streams : Marking 'complete' and then 'accept' change-set is not needed at repository workspace, change-set can be directly delivered to stream.
Hope my understanding is right.
Once a change set is in a stream it is delivered and completed.
Accept is always the option for incoming (completed) changes, regardless of incoming from a work item for example.
The available action for change sets that are in a repository workspace (or Stream) that flows to a Stream where the change set is not contained is deliver. Deliver completes a change set if it is not already completed.
Reading https://jazz.net/library/article/1439 provides the answer to the question around delivery between streams.