aboutsummaryrefslogtreecommitdiff
path: root/version-spec.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2017-09-20 09:55:42 -0400
committerNick Mathewson <nickm@torproject.org>2017-09-20 09:55:42 -0400
commitb50917d9c33d448947296472cc83e9f6ff1e98c9 (patch)
tree20bb912879daacb741fd876c53d4ad96f1ef3608 /version-spec.txt
parent7842a0621b90e61b45be34619dd3de5bca4bcbd6 (diff)
downloadtorspec-b50917d9c33d448947296472cc83e9f6ff1e98c9.tar.gz
torspec-b50917d9c33d448947296472cc83e9f6ff1e98c9.zip
version-spec: allow EXTRA_INFO to appear multiple times.
Diffstat (limited to 'version-spec.txt')
-rw-r--r--version-spec.txt5
1 files changed, 3 insertions, 2 deletions
diff --git a/version-spec.txt b/version-spec.txt
index 4a3dccf..1f25cd1 100644
--- a/version-spec.txt
+++ b/version-spec.txt
@@ -21,7 +21,7 @@
2. The New Way
After 0.1.0, versions are of the format:
- MAJOR.MINOR.MICRO[.PATCHLEVEL][-STATUS_TAG][ (EXTRA_INFO)]
+ MAJOR.MINOR.MICRO[.PATCHLEVEL][-STATUS_TAG][ (EXTRA_INFO)]*
The stuff in parentheses is optional. As before, MAJOR, MINOR, MICRO,
and PATCHLEVEL are numbers, with an absent number equivalent to 0.
All versions should be distinguishable purely by those four
@@ -38,7 +38,8 @@
The EXTRA_INFO is also purely informational, often containing information
about the SCM commit this version came from. It is surrounded by parentheses
and can't contain whitespace. Unlike the STATUS_TAG this never impacts the way
- that versions should be compared.
+ that versions should be compared. EXTRA_INFO may appear any number of
+ times. Tools should generally not parse EXTRA_INFO entries.
Now, we start each development branch with (say) 0.1.1.1-alpha. The
patchlevel increments consistently as the status tag changes, for