From 59b99fa6010b314c8c98fe738d9975f2c0afb219 Mon Sep 17 00:00:00 2001 From: Nick Mathewson Date: Mon, 23 Oct 2006 20:17:04 +0000 Subject: r9358@Kushana: nickm | 2006-10-23 12:02:25 -0400 clarify recent spec stuff svn:r8808 --- version-spec.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'version-spec.txt') diff --git a/version-spec.txt b/version-spec.txt index 5db2994..5b9aeee 100644 --- a/version-spec.txt +++ b/version-spec.txt @@ -32,9 +32,10 @@ All versions should be distinguishable purely by those four numbers. The status tag is purely informational, and lets you know how stable we think the release is: "alpha" is pretty unstable; "rc" is a release candidate; and no tag at all means that we have a final -release. If the tag ends with "-cvs", you're looking at a development -snapshot that came after a given release. If we *do* encounter two -versions that differ only by status tag, we compare them lexically. +release. If the tag ends with "-cvs" or "-dev", you're looking at a +development snapshot that came after a given release. If we *do* +encounter two versions that differ only by status tag, we compare them +lexically. Now, we start each development branch with (say) 0.1.1.1-alpha. The patchlevel increments consistently as the status tag changes, for -- cgit v1.2.3-54-g00ecf