Setting up parallel releases

Sometimes companies develop parallel releases of an application concurrently.

For example, one team might work on new features for release toolkit/3.0 of the toolkit application. Another team might work on bug fixes for release toolkit/2.1.

To build your application for more than one release, create a different project version for each developing release.

For example, your team is working on a new feature release called toolkit/3.0, and is concurrently working on a bug fix release called toolkit/2.1. You want the toolkit/3.0 release to include the bug fixes from release toolkit/2.1. However, you do not want the toolkit/2.1 release to include the features from toolkit/3.0.

You must modify the process rule for release toolkit/3.0 by adding the All Completed Tasks for Release toolkit/2.1 folder (not the folder template) to the toolkit/3.0 integration testing process rule. The toolkit/3.0 integration testing projects then pick up tasks from both releases. Make similar changes for the other process rules in the toolkit/3.0 release.

Developers still must merge parallel changes. If Joe changes a file in toolkit/3.0, then Mary changes the same file for toolkit/2.1, those changes are parallel. (Mary's change is chosen for toolkit/3.0 because it is newer.) The two versions must be merged into a new version for toolkit/3.0.


Feedback