%% subversion handling
% This file gives some guidelines in the subversion handling and includes:
%   1) repository layout
%   2) developer handling
%   3) merging and publishing

%% Repository layout
% The repository comprises the following directories with the corresponding
% use cases:
%   branch - with subfolders for each developer. Each developers
%       subdirectory contains the folders of the trunk and new or temporary
%       files and directories. Cross-merging between branches is NOT 
%       permitted.
%       Requirements: None
%   trunk - merges new developments of the branch. It's focus for use is
%       to ensure merged changes are properly working before going into
%       the pub directory. 
%       Requirements: all functions execute properly
%   pub - could be seen as a release candidate. The trunk is merged here,
%       while not all files and folders might enter the release.
%       Requirements: all functions execure properly, are documented and
%         are tested according to the toolboxLayer
%   tag - is used for publications. It might contain copies of all folders
%       above and the naming of the subfolders could be:
%         pub-version-1.0
%         branch-article-CES-May2050
%       at least the origin and, hence, the requirement level should be
%       indicated in the tag name.
%
% There are linux scripts that help with common operations, like: 
%   * updating pub from trunk
%   * merging a branch to the trunk
%   * merging a trunk to a branch

%% Branch folders
% * Do NOT commit binaries or images
% * use the svn:ignore feature to hide binary and reproducable content

%% Trunk folder
% * 