Changeset 365

Show
Ignore:
Timestamp:
02/27/06 23:59:08 (3 years ago)
Author:
edmanm
Message:

Make some changes to our versioning scheme.

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • trunk/doc/version-spec.txt

    r13 r365  
    55Vidalia releases will follow the following versioning convention: 
    66 
    7   Version ::= <MAJOR>.<MINOR>.<MICRO>[-<FLAG>] 
     7  Version ::= <MAJOR>.<MINOR>.<MICRO>[-svn] 
    88  MAJOR   ::= Integer >= 0 
    99  MINOR   ::= Integer >= 0 
    1010  MICRO   ::= Integer >= 0 
    11   FLAG    ::= alpha | beta | rc 
    1211 
    1312  MICRO will start at 1 and increase monotonically until a stable release, at 
    14   which point MINOR will be inremented and no flag identifier will be appended 
    15   to the version. MICRO will be set to 0 for a stable release and reset to 1 
    16   for the subsequent testing release. 
    17    
    18   FLAG indicates the release type and is one of the following: 
    19     alpha   An initial, unstable release. Some functionality may be broken or 
    20             unimplemented.. 
    21     beta    An unstable release, but most features should be functional. 
    22     rc      The developers expect this release to be stable, but more testing 
    23             needs to be completed. 
    24  
    25   Not all flags have to be used in a sequence of releases. For example, an -rc 
    26   release could immediately follow an -alpha release. 
     13  which point MINOR will be inremented MICRO will be set to 0 for a stable 
     14  release and reset to 1 for the subsequent testing release. 
    2715   
    2816  MAJOR will be incremented following several MINOR stable releases in which 
    2917  extensive functionality has been added or modified. Developers will use 
    3018  their discretion in determining MAJOR releases. 
     19   
     20  The -svn flag will be used to denote the latest snapshot in the Subversion 
     21  repository. It will be removed for an official release. For example, 
     22  0.0.2-svn would become 0.0.2 when it is officially released. 
    3123 
    3224  An example of a possible sequence of versions is as follows: 
    3325 
    34     0.0.1-alpha  __ 
    35     0.0.2-alpha   | 
    36     0.0.3-beta    |-  Testing 
    37     0.0.4-rc     _| 
    38     0.1.0         ]-  Stable 
    39     0.1.1-alpha  -- 
    40     0.1.2-rc      |-  Testing 
    41     0.1.3-rc     _| 
    42     1.0.0         ]-  Stable 
     26    0.0.1 
     27    0.0.2 
     28    0.0.3 
     29    0.1.0  <-- Stable 
     30    0.1.1 
     31    0.1.2 
     32    0.1.3 
     33    1.0.0  <-- Stable