Subversion Structure

The project Version Control System (VCS) directory structure.
The standard subversion (svn) conventions of trunk/, branches/ and tags/ have been followed and then elaborated on.

trunk/ - Contains all leading edge development work.

doc/
grails-app/
util-apps/
web-app/
README
COPYING
INSTALL

branches/ - Contains working branches.

custom/ - Customised branches for particular customers.

customX/releases/
customY/releases/

doc-releases/ - Documentation release preparation (branch off /trunk/doc/).

1.0.x/
1.1.x/

releases/ - Application release preparation (branch off /trunk) - excludes doc, util-apps etc.

1.0.x/
1.1.x/

features/ - Feature development branches.

featureX/
featureY/

tags/ - Contains tagged points in time (NEVER commit software development to tags).

doc-releases/ - Public documentation releases (tag of a doc branch).

1.0.0-DOC1/
1.0.0-DOC2/

releases/ - Public application releases (tag of a release branch).

1.0.0/
1.0.1/

release-candidates/ - Release candidates (tag of a release branch).

1.0.0-RC1/
1.0.0-RC2/

Where:
Application releases are tagged with MAJOR.MINOR.VERSION numbers.
Documentation releases are tagged to match the application release but with a -DOCn suffix.
This allows corrective releases to be made for documentation while keeping the MAJOR.MINOR.VERSION numbers in sync with the application release.