Whether or not you are part of a team, you can create a stream to hold the versions of components that represent an important configuration of a system. A milestone release of a software development project is an example of one such configuration. A stable version of a third-party or open source software package is another. When team members deliver change sets from their workspaces to a stream and accept change sets delivered to the stream by other team members, the stream represents the current state of the team's development effort. When deliveries to a stream are constrained by process controls (requiring code to be free of compilation errors, or reviewed and approved before delivery), the stream becomes a stable source of shared artifacts. All streams are flow targets of workspaces or other streams. Some streams (such as integration streams) have their own flow targets, which are typically established when the stream is created.
A stream can include zero or more components. Any component in the repository can be made part of a stream, though typically the components in a stream have dependencies or functional relationships that make it sensible to group them. After you have created a stream, you can use the Stream editor to add components to it, remove them from it, or change the versions of one or more components in the stream.
To create a stream:
Did this help? You can provide feedback at Jazz.net (registration required): Comment in the forums or submit a bug