You may have noticed by now that Subversion is extremely
flexible. Because it implements branches and tags with the same
underlying mechanism (directory copies), and because branches
and tags appear in normal filesystem space, many people find
Subversion intimidating. It's almost
flexible. In this section, we'll offer some suggestions for
arranging and managing your data over time.
There are some standard, recommended ways to organize a
repository. Most people create a
directory to hold the “main line” of development,
branches directory to contain branch
copies, and a
tags directory to contain
tag copies. If a repository holds only one project, then
often people create these top-level directories:
If a repository contains multiple projects, admins
typically index their layout by project (see
the section called “Choosing a Repository Layout” to read more about
Of course, you're free to ignore these common layouts.
You can create any sort of variation, whatever works best for
you or your team. Remember that whatever you choose, it's not
a permanent commitment. You can reorganize your repository at
any time. Because branches and tags are ordinary directories,
command can move or rename
them however you wish. Switching from one layout to another
is just a matter of issuing a series of server-side moves; if
you don't like the way things are organized in the repository,
just juggle the directories around.
Remember, though, that while moving directories may be
easy to do, you need to be considerate of your users as well.
Your juggling can be disorienting to users with existing
working copies. If a user has a working copy of a particular
repository directory, your
operation might remove the path from the latest revision.
When the user next runs
, she will
be told that her working copy represents a path that no
longer exists, and the user will be forced to
to the new location.