Release Candidate Development Using Branches

These are the steps you will take when you want to create a branch based on the release candidate. These are not common. The release candidate does tend to persist for a few months after a release in support of patch releases. Since patch releases are inherently limited in scope, there is not much reason to use branches other than for testing on various platforms without making a regular RC check-in.

What you want	How you do it
To create a branch from the RC (i.e. ClearCase mkrcdev)	Script: mk_branch_from_rc
To checkout the RC branch directory (i.e. ClearCase ct setview -login)	Script: co_branch
To bring in changes that were put on the RC	Script: merge_RC_to_branch
To bring in changes made directly on your RC development branch that occurred after the checkout. One example of a change of this type would include you doing work on another machine on this RC development branch, doing a commit, and then wanting to pick up these change. Another example would be if another developer was collaborating on this same RC development branch. Outside of these examples, you probably will not need this use case.	SVN command: svn update
To check in your changes to your own branch	SVN command: svn commit
To merge your changes to the RC	Script: merge_branch_to_RC
To destroy the record of the branch in the SVN repository.	Script: del_branch
To remove the directory on your personal file system that was a checkout of a SVN branch.	Unix command: rm -Rf