Managing components

In Rational Synergy, a release specifies the release label of your software application, for example, Rational Synergy/7.1 or Rational Change/5.2. Releases are like versions, but they apply to an entire software product. A release can represent a product you have already delivered (or released), or it can represent a release you are currently developing. Each project is typically marked for a specific release, as is each task.

Each component must have its own release stream. For example, consider a team who develops a GUI library and two applications: a calculator and an editor. They might set up releases like the following example.

Component
Release Streams
GUI library
gui_lib/1.1, gui_lib/1.2, gui_lib/1.3
Editor application
editor/1.0, editor/2.0, editor/2.1, editor/3.0, editor/4.0
Calculator application
calc/1.0, calc/2.0

The purpose of setting up a different release stream for each component is to decouple the different components so they are independent of one another. This enables the components to be on different release schedules, and ensures that the development teams can use different processes if they choose.


Feedback