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.

1. She requests mastership of the branch type:

   cleartool reqmaster –c "merging party in Boston" brtype:main@/vobs/html
   brtype:main@/vobs/html: Change of mastership at sibling replica "sanfran_hub"
   was successful.
   Mastership is in transit to the new master replica.
   

2. Periodically, she displays properties of the branch type to determine whether mastership has been received. After mastership is received at her replica, the describe command shows that her replica masters the branch type.

   cleartool describe –fmt "%[master]p\n" brtype:main@/vobs/html
   boston_hub@/vobs/html
   

All of the branches that had default mastership are now mastered by the Boston replica. If any of the branches were explicitly mastered by the San Francisco or Tokyo replicas, their mastership was not changed. Developers must request mastership for those specific branches.

The developers in Boston can perform necessary merges and check in their changes.