What is a generic name for SVN's "trunk", "tags" and "branches" directories?

Question

The recommended Subversion directory layout contains trunk, tags and branches directories:

Project
|-branches
  |- ...
|-tags
  |- ...
|-trunk

Is there a generic name for referring to the three directories: trunk, tags, and branches? Let's say for naming a variable: list x = ["branches/...", "tags/...", "trunk" ].)

Answer 1

I have seen it called the common repository layout. See Use a sane repository layout and Repository Layout.

So, I guess you could call them the common repository layout directories. (That is not much shorter than enumerating them though.:-)

So, for naming a variable: commonRepoDirs or common_repo_dirs (depending on the conventions of your programming language).

Answer 2

Base on what I observed in different open source projects, I usually use this convention (Assume we are adopting trunk-based development, and making use of release-branch and feature-branch branching strategies)

Basic layout:

+ proj-name
  + trunk        // trunk
  + tags         // tags
  + branches     // release branches
  + sandboxes    // feature branches

Directory name for trunk/tags/branches are pretty standard. I usually separate feature branches from release branches to avoid confusion. However there is no standard directory for feature branches. "sandboxes" are one name that I have seen. You can consider something else you like

For tag name, quite a lot of project use proj-name-VERSION. For example, tag for foo project version 1.2.3 is going to be tagged as foo-1.2.3

For branch name, it depends on how you arrange your version and release. One typical way is having version as MAJOR.MINOR.MICRO. Incrementation of MAJOR or MINOR is going to be a new release, while MICRO is used for bug fixes for a release. In such case, we usually create release branch for MAJOR.MICRO.x. For example, upon release of foo version 1.0, you should create a release branch for foo version 1.0.x. Branch name is usually foo-1.0 or foo-1.0.x

For feature branches, simply name it base on the feature. No special convention I observed.