Model repository versions: Difference between revisions

From CSDMS
m (Created page with "=Model repository versions= CSDMS uses subversion for its model repository. Subversion is an open source version control system, keeping track of version updates of models, using...")
 
m (Tidied up descriptions)
Line 1: Line 1:
__NOTOC__
=Model repository versions=
=Model repository versions=
CSDMS uses the open source version control system, [http://subversion.apache.org/ Subversion] to maintain model repositories. The base of every repository contains the usual '''trunk''', '''tags''', and '''branches''' directories.
CSDMS uses subversion for its model repository. Subversion is an open source version control system, keeping track of version updates of models, using '''tags''', '''trunk''' and '''branches'''.  
CSDMS uses subversion for its model repository. Subversion is an open source version control system, keeping track of version updates of models, using '''tags''', '''trunk''' and '''branches'''.  
==trunk==
The trunk contains up-to-date versions of model source code that developers have submitted. Because this is the "main line" of development, keep in mind that the trunk may be used for active development and so could contain unstable code.
==tags==
==tags==
Tags are often used for stable versions of a model. Behind the '''tags''' label you often see a version number (e.g. tags/0.1.0) or a release date.
A tag is just a snapshot of a project in time. A model developer will often tag a particular snapshot with a human friendly name, such as <tt>release-1.0</tt> (or a date, of just a version number).  
==trunk==
 
The trunk contains nightly builds or latest model updates submitted by the developer to subversion. So keep in mind that the trunk is often used by developers of the code and it could contain a not stable version of the source code as development is still occurring.
==branches==
==branches==
A branch is a side-line of development created to make larger, experimental or disrupting work without annoying users of the trunk version. Also, branches can be used to create development lines for multiple versions of the same product, like having a place to backport bugfixes into a stable release.
A branch is a line of development parallel to the trunk.  Branches are often created for one of two reasons:
# to make larger, experimental or disrupting changes without annoying users working on the trunk or
# to maintain a mainentance line of development for older project releases.

Revision as of 11:06, 21 February 2011

Model repository versions

CSDMS uses the open source version control system, Subversion to maintain model repositories. The base of every repository contains the usual trunk, tags, and branches directories.

CSDMS uses subversion for its model repository. Subversion is an open source version control system, keeping track of version updates of models, using tags, trunk and branches.

trunk

The trunk contains up-to-date versions of model source code that developers have submitted. Because this is the "main line" of development, keep in mind that the trunk may be used for active development and so could contain unstable code.

tags

A tag is just a snapshot of a project in time. A model developer will often tag a particular snapshot with a human friendly name, such as release-1.0 (or a date, of just a version number).

branches

A branch is a line of development parallel to the trunk. Branches are often created for one of two reasons:

  1. to make larger, experimental or disrupting changes without annoying users working on the trunk or
  2. to maintain a mainentance line of development for older project releases.