Branching in sharpcvslib has been used primarily to maintain a stable code base for releases. With this in mind the strategy for branching (at the time this document was written) is to branch when the code is feature complete for the release and nearing a stable condition. A branch will then be made with the intent that only minor bug fixes will be applied to the branch.
When it is nearing time for another release the process will be completed and the existing branch will then be conceptually marked "closed". The stabalization process will then repeat for the new release cycle.
Branch Name | Purpose | Active |
Release_0_35_branch | Maintenance of Release 0.35 | true |
Developer:
cvs -d:ext:[username]@cvs.sourceforge.net:/cvsroot/sharpcvslib co -r [branch_name] -d [override_directory] sharpcvslib
Anonymous:
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/sharpcvslib co -r [branch_name] -d [override_directory] sharpcvslib
where:
[branch_name]
: the name of the branch you are interested in, for instance Release_0_35_branch.
[override_directory]
: the directory that the sources should be checked out in instead of the module directory, for instance use sharpcvslib_0_35_branch.