Home Explore Help
Sign In
piros
/
tor
3
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Tree: d230827912
Branches Tags
tor
/
doc
/
spec
/
version-spec.txt

version-spec.txt 2.1 KB
History Raw

1234567891011121314151617181920212223242526272829303132333435363738394041424344 
  1. 

  2.                         HOW TOR VERSION NUMBERS WORK
    3. 

  3. 

  4. 1. The Old Way
    5. 

  5. 

  6.  Before 0.1.0, versions were of the format:
    7. 

  7.      MAJOR.MINOR.MICRO(status(PATCHLEVEL))?(-cvs)?
    8. 

  8.  where MAJOR, MINOR, MICRO, and PATCHLEVEL are numbers, status is one
    9. 

  9.  of "pre" (for an alpha release), "rc" (for a release candidate), or
    10. 

  10.  "." for a release.  As a special case, "a.b.c" was equivalent to
    11. 

  11.  "a.b.c.0".  We compare the elements in order (major, minor, micro,
    12. 

  12.  status, patchlevel, cvs), with "cvs" preceding non-cvs.
    13. 

  13. 

  14.  We would start each development branch with a final version in mind:
    15. 

  15.  say, "0.0.8".  Our first pre-release would be "0.0.8pre1", followed by
    16. 

  16.  (for example) "0.0.8pre2-cvs", "0.0.8pre2", "0.0.8pre3-cvs",
    17. 

  17.  "0.0.8rc1", "0.0.8rc2-cvs", and "0.0.8rc2".  Finally, we'd release
    18. 

  18.  0.0.8.  The stable CVS branch would then be versioned "0.0.8.1-cvs",
    19. 

  19.  and any eventual bugfix release would be "0.0.8.1".
    20. 

  20. 

  21. 2. The New Way
    22. 

  22. 

  23.  After 0.1.0, versions are of the format:
    24. 

  24.     MAJOR.MINOR.MICRO(.PATCHLEVEL)(-status_tag)
    25. 

  25.  The stuff in parentheses is optional.  As before, MAJOR, MINOR, MICRO,
    26. 

  26.  and PATCHLEVEL are numbers, with an absent number equivalent to 0.
    27. 

  27.  All versions should be distinguishable purely by those four
    28. 

  28.  numbers. The status tag is purely informational, and lets you know how
    29. 

  29.  stable we think the release is: "alpha" is pretty unstable; "rc" is a
    30. 

  30.  release candidate; and no tag at all means that we have a final
    31. 

  31.  release. If the tag ends with "-cvs" or "-dev", you're looking at a
    32. 

  32.  development snapshot that came after a given release.  If we *do*
    33. 

  33.  encounter two versions that differ only by status tag, we compare them
    34. 

  34.  lexically.
    35. 

  35. 

  36.  Now, we start each development branch with (say) 0.1.1.1-alpha.  The
    37. 

  37.  patchlevel increments consistently as the status tag changes, for
    38. 

  38.  example, as in: 0.1.1.2-alpha, 0.1.1.3-alpha, 0.1.1.4-rc, 0.1.1.5-rc.
    39. 

  39.  Eventually, we release 0.1.1.6.  The next patch release is 0.1.1.7.
    40. 

  40. 

  41.  Between these releases, CVS is versioned with a -cvs tag: after
    42. 

  42.  0.1.1.1-alpha comes 0.1.1.1-alpha-cvs, and so on. But starting with
    43. 

  43.  0.1.2.1-alpha-dev, we switched to SVN and started using the "-dev"
    44. 

  44.  suffix instead of the "-cvs" suffix.
    45.