aboutsummaryrefslogtreecommitdiff
path: root/spec/version-spec.md
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2023-10-13 18:00:42 -0400
committerNick Mathewson <nickm@torproject.org>2023-10-13 18:00:42 -0400
commitf79272ef1f774b3788b74a3fe4fef75095dfae06 (patch)
tree8f47bebaa06c444f632bf8c4afbd793c4972a27d /spec/version-spec.md
parentfa014ec90411fd754dd257d04afa1a953e15bf31 (diff)
downloadtorspec-f79272ef1f774b3788b74a3fe4fef75095dfae06.tar.gz
torspec-f79272ef1f774b3788b74a3fe4fef75095dfae06.zip
Run markdownlint --fix on spec.
Diffstat (limited to 'spec/version-spec.md')
-rw-r--r--spec/version-spec.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/spec/version-spec.md b/spec/version-spec.md
index 296839b..a4b6373 100644
--- a/spec/version-spec.md
+++ b/spec/version-spec.md
@@ -9,6 +9,7 @@ Table of Contents
```
<a id="version-spec.txt-1"></a>
+
# The Old Way
Before 0.1.0, versions were of the format:
@@ -29,6 +30,7 @@ say, "0.0.8". Our first pre-release would be "0.0.8pre1", followed by
and any eventual bugfix release would be "0.0.8.1".
<a id="version-spec.txt-2"></a>
+
# The New Way
Starting at 0.1.0.1-rc, versions are of the format:
@@ -65,7 +67,8 @@ Between these releases, CVS is versioned with a -cvs tag: after
suffix instead of the "-cvs" suffix.
<a id="version-spec.txt-3"></a>
-# Version status.
+
+# Version status
```text
Sometimes we need to determine whether a Tor version is obsolete,
@@ -90,4 +93,3 @@ suffix instead of the "-cvs" suffix.
* Finally, if none of the above conditions hold, then the version is
"un-recommended."
```
-