Branch, tag and merge changes

Subversion supports separate lines of development within a project. These lines are isolated within the repository, but you can compare, copy, and merge their content.

Branching: A branch starts as a copy of a main line of development, but continues independently thereafter, with its own changes. You may need to create a branch, for example, if you plan to start working on a major new feature and do not want to affect the main line of development.
Tagging: A tag is a static snapshot of a particular revision of the repository. Usually you create a tag when your project reaches a milestone or the product is ready for release. By convention, you do not commit changes to a tag, although it is possible.
Merging: When development on a branch reaches a particular stage, the changes are generally merged into the main line of development. For example, if your work on the new feature is stable, the changes in the branch can be merged to the trunk.

Create a branch or tag
Creating a tag is no different from creating a branch. For both, Subversion uses a "cheap copy" or an internal link to a specific revision. The two differ in how they are used.
Switch to a branch
To switch your working copy from the line of development you're working on to a branch or tag, use the Switch Solution option.
Merge changes
When your project involves different lines of development, at some point you will need to merge your changes from a branch to trunk or to a different branch.

Up: Version control operations

Related actions

Switch to a branch

More information

Version control with Subversion - Branching and Merging