Next: An example: releasing a
Up: Tags and Branches
Previous: Merging branches
Contents
It is a widely-used to pattern to create tags from a branch when the
code in the branch is stable or has implemented some features. Since
in Subversion the whole repository has one global revision, the tags
are just symbolic names for a revision. They are useful however
because they are usually meaningfull names following some predefined
release numbering convention. For example, tag-2.5.6 might
means that this is the 6th patch of the 5th branch of the 2nd version
of the project. A simple scenario for tag usage is the following - the
development team fix bugs and implement features. At some point of
time they tag the branch they work on and ask the QA team to take the
source, build it and test it.
Tags are created with svn copy command in the same way as
branches:
$ svn copy
https://localhost/svn/repo1/helloworld/branches/br-0.8
https://localhost/svn/repo1/helloworld/tags/tag-0.8.1
Now we should only ensure that the contents of the tags is not
modified. It can be easily done with authorization options.
Ivan Ivanov
2008-04-21