Subversion Usage In Argeo

From ArgeoWiki

This page describes the naming conventions when using Subversion for managing development project in the Argeo infrastructure. More general information about Subversion can be found here.

Contents 1 General principles 1.1 Access rights 1.2 Development process 2 Naming Conventions 2.1 Project root URL 2.2 Tags 2.3 Branches

General principles

Access rights

Public project sources are readable by anyone. Only logged in committers can commit changes. There are no other restrictions or rights on the public repository, committers are supposed to be responsible enough not to mess up with other projects codes.

Private projects sources are available only to project committers and each project has its own repository.

Development process

The current development stream (odd minor version) is managed in the trunk codeline. Maintenance streams (even minor versions) are managed in branches.

See Development Process for more details on development procedures.

Naming Conventions

Project root URL

The SVN project root URL for a public project, named projectName, is:

https://www.argeo.org/svn/<projectName>

The SVN project root URL for a private project, named projectName, is:

https://www.argeo.org/private/projects/<projectName>/svn

Tags

Tags are named after the release version, without a 'v'. For example:

<project root URL>/tags/0.2.1

Branches

• Maintenance stream branches are name after the major.minor of the version, without a 'v'. For example:

<project root URL>/branches/0.2

• Individual developer branches are named after the technical name of the user. For example:

<project root URL>/branches/mbaudier

• Ad-hoc branches for subprojects can be named freely. It is of course recommanded that the naming is consistent within the project. For example:

<project root URL>/branches/refactoring_xmlserialization