/[MITgcm]/mitgcm.org/cvspolicy.html
ViewVC logotype

Diff of /mitgcm.org/cvspolicy.html

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph | View Patch Patch

revision 1.3 by cnh, Sun Jul 2 14:59:56 2000 UTC revision 1.5 by cnh, Sun Jul 2 15:03:23 2000 UTC
# Line 24  o Why have a policy? Line 24  o Why have a policy?
24    The policies we employ address two areas    The policies we employ address two areas
25      1. Maintaining an orderly and easily identifiable, coherent set of      1. Maintaining an orderly and easily identifiable, coherent set of
26         evolving "products".         evolving "products".
27      2. Allowing concurrent, on-going development of products.      2. Allowing concurrent, on-going development of product components.
28        
29  o Development trees and checkpoint trees  o Development trees and checkpoint trees
30        
# Line 41  o Development tree policies Line 41  o Development tree policies
41    a particular person, a certain project or a particular special piece of    a particular person, a certain project or a particular special piece of
42    work. These trees are intended to be useful areas for storing current    work. These trees are intended to be useful areas for storing current
43    work and for archiving partially finished work so that it doesn't get    work and for archiving partially finished work so that it doesn't get
44    mislaid and s that some record of the development history can be easily    mislaid and so that some record of the development history can be easily
45    maintained. The only policy that applies to development trees is that    maintained. The only policy that applies to development trees is that
46    this style of tree is not intended to be used for providing a    this style of tree is not intended to be used for providing a
47    "checkpoint" distribution. Tagged configurations of tools built from this    "checkpoint" distribution. Tagged configurations of tools built from this
48    style of tree can be distributed, but because these trees do not have any    style of tree can be distributed, but because these trees do not have any
49    polcies regarding testing of functionality, platform coverage or    polcies regarding testing of functionality, platform coverage or
50    documentation these trees are not allowed to form the basis of    documentation these trees are not allowed to form the basis of
51    "checkpoint" distrbutions or formal model releases. Other policies can    "checkpoint" distrbutions or formal "releases". Other policies can
52    be defined by individuals users of these trees but there are no further    be defined by individuals users of these trees but there are no further
53    global policies. The MITGCM repository development/ subdirectory is    global policies. The MITGCM repository development/ subdirectory is
54    reserved for holding development trees. Development trees also serve as    reserved for holding development trees. Development trees also serve as
Legend:
Removed from v.1.3  
changed lines
  Added in v.1.5
  ViewVC Help
Powered by ViewVC 1.1.22