Hi,

that sounds strange.

RTC supports selective check in and delivery of change sets. It is even possible to reorganize changes in separate change sets later.

It is also possible to suspend and resume separate change sets.

The UI allows to select a change set and just check in and deliver this specific change set. The controlling element is where you right click the outgoing changes. If you right click a single change set you deliver just that. If you right-click on outgoing you deliver all change sets.

You mention checking in and deliver change sets below. Actually you don't check in a change set. You create a change set when checking in or you add a change to a change set. After this has been done the change sets can be delivered.

There is a difference between change and change set. Changes are changes to files. Change sets are objects that accumulate changes in the SCM system.

I suspect from your description what happened is, there where several outgoing changes locally that needed check in. The users selected the unresolved node and selected checkin and deliver. The result is that the changes where subsumed into a new change set and delivered.

In this situations I typically do a check in first. Either on all changes or just on separate ones. A change set gets created for the change if none exists. It is also possible to select the desired change set to add the change If one already exists. After I am happy with the distribution of the changes into their change sets (and the work items associated) I deliver singe or multiple change sets to the stream.


Ralph