The standard ClearCase development model is to use branches to develop software in parallel, and the standard MultiSite model is to master different branch types at different replicas so that development can proceed concurrently at different replicas. These models require you to merge changes from branch to branch.
However, sometimes sites must use serial development (for example, to make changes to elements whose versions cannot be merged). To support serial development, there are two models for changing mastership:
The developer who needs to work on a branch asks the administrator of the master replica to transfer mastership of the branch and send an update packet containing the change.
The developer who needs to work on a branch requests mastership of the branch. This model is not enabled by default, and it requires the MultiSite administrator to enable requests and authorize developers to request mastership. However, after the setup is complete, the administrator does not need to be involved in the mastership request process.
Note: The developer can also request mastership of branch types. For more information, see Implementing Requests for Mastership.
There are two ways to use requests for mastership:
For more information about enabling requests for branch mastership, see Implementing Requests for Mastership. For more information about the use models for requesting mastership, see Working On a Team in Developing Software.