version-spec.txt 2.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445
  1. $Id$
  2. HOW TOR VERSION NUMBERS WORK
  3. 1. The Old Way
  4. Before 0.1.0, versions were of the format:
  5. MAJOR.MINOR.MICRO(status(PATCHLEVEL))?(-cvs)?
  6. where MAJOR, MINOR, MICRO, and PATCHLEVEL are numbers, status is one
  7. of "pre" (for an alpha release), "rc" (for a release candidate), or
  8. "." for a release. As a special case, "a.b.c" was equivalent to
  9. "a.b.c.0". We compare the elements in order (major, minor, micro,
  10. status, patchlevel, cvs), with "cvs" preceding non-cvs.
  11. We would start each development branch with a final version in mind:
  12. say, "0.0.8". Our first pre-release would be "0.0.8pre1", followed by
  13. (for example) "0.0.8pre2-cvs", "0.0.8pre2", "0.0.8pre3-cvs",
  14. "0.0.8rc1", "0.0.8rc2-cvs", and "0.0.8rc2". Finally, we'd release
  15. 0.0.8. The stable CVS branch would then be versioned "0.0.8.1-cvs",
  16. and any eventual bugfix release would be "0.0.8.1".
  17. 2. The New Way
  18. After 0.1.0, versions are of the format:
  19. MAJOR.MINOR.MICRO(.PATCHLEVEL)(-status_tag)
  20. The stuff in parentheses is optional. As before, MAJOR, MINOR, MICRO,
  21. and PATCHLEVEL are numbers, with an absent number equivalent to 0.
  22. All versions should be distinguishable purely by those four
  23. numbers. The status tag is purely informational, and lets you know how
  24. stable we think the release is: "alpha" is pretty unstable; "rc" is a
  25. release candidate; and no tag at all means that we have a final
  26. release. If the tag ends with "-cvs" or "-dev", you're looking at a
  27. development snapshot that came after a given release. If we *do*
  28. encounter two versions that differ only by status tag, we compare them
  29. lexically.
  30. Now, we start each development branch with (say) 0.1.1.1-alpha. The
  31. patchlevel increments consistently as the status tag changes, for
  32. example, as in: 0.1.1.2-alpha, 0.1.1.3-alpha, 0.1.1.4-rc, 0.1.1.5-rc.
  33. Eventually, we release 0.1.1.6. The next patch release is 0.1.1.7.
  34. Between these releases, CVS is versioned with a -cvs tag: after
  35. 0.1.1.1-alpha comes 0.1.1.1-alpha-cvs, and so on. But starting with
  36. 0.1.2.1-alpha-dev, we switched to SVN and started using the "-dev"
  37. suffix instead of the "-cvs" suffix.