Changeset for multiple streams. Ignore or mark complete permanently
Here is my scenario. making an example for it.
Consider: 2 Streams A & B, work item x
I delivered a change set for work item x to Stream A.
When I do comparison of Stream A & B, found that the same change set is not delivered in Stream B.
I have two choices, either I promote (deliver) the change set to stream B or don't do anything.
If I don't do anything, than in next comparison the same change set will show up as a missing item in Stream B.
I like to mark the change set NOT needed, or deliver it empty, or discard in a way that the comparison of stream should not reflect after first time.
How I can achieve this goal.
We need to keep in mind that we will always compare streams not work space.
I appreciate all inputs.
Consider: 2 Streams A & B, work item x
I delivered a change set for work item x to Stream A.
When I do comparison of Stream A & B, found that the same change set is not delivered in Stream B.
I have two choices, either I promote (deliver) the change set to stream B or don't do anything.
If I don't do anything, than in next comparison the same change set will show up as a missing item in Stream B.
I like to mark the change set NOT needed, or deliver it empty, or discard in a way that the comparison of stream should not reflect after first time.
How I can achieve this goal.
We need to keep in mind that we will always compare streams not work space.
I appreciate all inputs.
2 answers
I guess your two streams contain same set of components and are equivalent. The comparison will always show the missing changeset until you accept it and possibly merge it. The two streams may contain different set of changesets possibly because they represent two different releases of the product. In that case, you do want to know the differences when you compare. Making the two streams look the same without accepting the changes is not the right thing to do.
Comments
I believe you are looking for the functionality requested by: Provide a "reject" operation that can be applied to a set of incoming change sets (159380) . This functionality is not yet supported by RTC.
As a workaround, you can create a new stream, named something like "Reviewed-work-items". After you have reviewed a set of incoming changes, accept them into this new stream. Then you can cherry pick incoming work items from the stream to the Reviewed-work-items stream.
As a workaround, you can create a new stream, named something like "Reviewed-work-items". After you have reviewed a set of incoming changes, accept them into this new stream. Then you can cherry pick incoming work items from the stream to the Reviewed-work-items stream.
Comments
