Changes between Version 5 and Version 6 of BranchingPolicy


Ignore:
Timestamp:
08/26/10 14:42:33 (4 years ago)
Author:
dread
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • BranchingPolicy

    v5 v6  
    33CKAN is stored in a mercurial repo and we have devised this policy to cope with coding, releasing and maintaining versions of the software. 
    44 
    5 This policy reflects Python development ( http://www.python.org/dev/peps/pep-0374/#backport ), but instead of naming branches after their version numbers, they are named after the stability of the release. This allows `metastable` to always to be a beta, `stable` to be the latest solid release and `ultrastable` to be the previous-but-one release. 
     5This is based on the [http://www.python.org/dev/peps/pep-0374/#backport system used to develop Python], but instead of naming branches after their version numbers, they are named after the maturity of the release, which suits our more frequent releases. This allows `metastable` to always to be a beta, `stable` to be the latest solid release and `ultrastable` to be the previous-but-one release. 
    66 
    77== Branches ==