Releasing

As you make changes locally in your workbench, you are working isolated from the rest of the team. When you are ready to make your local resource changes available to other team members, you'll need to release your work to the stream. All such changes are termed as outgoing changes when you do a synchronization.

Catch Up First

Ideally, you should catch up to a stream before releasing to it. This ensures that you have the very latest work from the other team members. After you have caught up with the stream, merged any conflicting changes in your local workbench, and tested your changes locally, you can more easily release your workbench's changes to the stream.

What Other Team Members See

When you release changes to the stream, your changes are copied from your local workbench to the stream. As a result, these changes are then seen as incoming changes when other developers catch up to the stream later.

Release Views

Related Topics:

  • See Team Programming Model
  • See Synchronizing
  • See Catching Up
  • See Dealing With Conflicts
  • Structure Compare Pane

    This pane allows you to view the high-level structural differences between a stream resource and a local workbench resource.

    Source Compare Pane

    This pane allows you to see specific, line-by-line differences between a stream resource and a local workbench resource.