Requesting mastership
This scenario provides examples of how the writers
use mastership requests to do their work.
- Serial development of a file that cannot be merged
In this scenario, a writer cannot currently check out the file using a reserved checkout because the branch is mastered by a different replica. She waits until she receives mastership before proceeding with her checkout. - Serial development of a file that can be merged
In this scenario, a writer cannot currently check out the file using a reserved checkout because the branch is mastered by a different replica. He checks out the file using the –unreserved and –nmaster options. After he receives mastership, he finds that he must merge the changes before he can complete his checkin operation. - Requesting mastership of a branch type
In this scenario, the Boston developers have been using nonmastered checkouts to work on scripts, and their project leader decides that all the changes need to be checked in. To reduce the number of mastership requests for individual branches, the project leader requests mastership of the main branch type.
Parent topic: Serial development scenario