A change set is a repository object of Jazz which contains related files, folders and other modifications within a component of a stream in Source Control Management.
The change set is the most basic unit of change in Rational Team Concert™ source control management. A change set can include changes to the individual files’ content and changes to a component (like delete, rename, etc.)
A change set is basically a collection of related changes to files or folders that are present in a flow target. You can see the Change sets in the Pending Changes window of RTC Eclipse IDE. Change Sets creates the storage model of RTC. They are the base currency and can be shared (through work items), suspended, discarded, and reverted.
When you save your changes, changes will be appeared in Pending Changes window as Change Set. You create change sets by making changes in files in your sandbox, then committing to a repository workspace, which backs up and records the changes.
The changed source will be in Pending Changes > Unresolved
Right click the Unresolved folder then Check-in > New Change Set.
now those changes will come to Outgoing.
We call a change set as incoming when it is present in a workspace flow target but not in your own workspace.
You can see the Incoming folder in the Pending Changes view. You can accept an incoming change set to add it to your repository workspace and then load it into your sandbox.
In case, an accepted change causes any errors in your workspace, you have an option to discard it. In this way, that change set will be unloaded from your sandbox, from your repository workspace, and it will be moved to the Incoming folder, hence undoing the accept operation.
We call a change set as outgoing when it is present in your own workspace but not in its flow targets.
You can see the Outgoing folder In the Pending Changes view like Incoming folder.
The following operations can be performed for an outgoing change set:
After marking it Delivered it will flow to the current flow target of the workspace.
The Suspended change set will be removed from the sandbox, but it will be saved in your repository for future resuming. The changes in the change set revert to the state they were in before the first change was made.
When the change set is discarded, all its items will be revert back to the state they were in before the first change was made. After discarding a change set, all changes will be undone on permanent basis.
You can create a new, empty change set any time.
Change set should be delivered so that team can view them, Prior delivering change sets, check in the changes.
Incoming change sets are the change sets that your team delivered to current flow target. They will be shown in the Incoming folder of the Pending Changes.
You can suspend any change set at any point int time if you need to remove from your repository workspace but still want to preserve it in the repository. This change set can be restored any time when you want to resume your work. Prior to suspending a change sets, you have to check in the changes.
You can resume a change set which was previously suspended due to any reason.
If any change set is of no use or causing an error in the source it can be discarded. You can discard either a outgoing change set or an accepted change set.
When you have done with the work, you can make a change set Complete. A completed change set will no longer be active. Prior to completing a change set, you have to check it in the change set.
By reversing a change set, you can remove the changes present in that change set. It will create a patch. On merging the patch in your repository workspace, the changes made to the selected change set are removed and a new change set will be created. This new change set can be delivered to reverse the changes in the workspace flow target.
You can move any important files/folders to a change set.
You can associate a work item with change set(s).
By viewing the change sets associated with work items will give you complete information about the changes that happened throughout the life cycle of the work item.
With the help of Change Summary, you can review changes to files and folders and view information about individual change sets that modified a file or folder. You can also use the Change Explorer window to compare change sets in different work spaces, streams, snapshots, or baselines.
You can find out change sets‘ streams, repository workspace, or snapshots that it belongs to.
With the help of this post, any developer can easily learn to work with change sets in RTC SCM Model at beginner level.