The build manager for a component development shop releases several component baselines many times a week. After a version of the component is released, the build manager must create the next release so work can begin on it immediately. On Monday morning, the build manager releases the siriusCore/4.3.25-006 component and needs the team to begin work on siriusCore/4.3.25-007 Monday afternoon.
The build manager copies the siriusCore/4.3.25-006 release. (The Copy Release dialog box pre-populates the release field with siriusCore/4.3.25-007.) The team is notified that the new siriusCore/4.3.25-007 release is ready; the team can perform a Refresh Choices operation to get the new release value and begin working.
If your team develops more than one release of an application concurrently, they support parallel releases.
For example, one team might work on new features for release toolkit/3.0 of the toolkit application while another team works on bug fixes for release toolkit/2.1.
Support parallel releases by creating one integration build management project hierarchy and one system test build management project hierarchy for each unique release combination.