summaryrefslogtreecommitdiff
path: root/doc/HACKING/EndOfLifeTor.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/HACKING/EndOfLifeTor.md')
-rw-r--r--doc/HACKING/EndOfLifeTor.md7
1 files changed, 3 insertions, 4 deletions
diff --git a/doc/HACKING/EndOfLifeTor.md b/doc/HACKING/EndOfLifeTor.md
index cada2da7fb..0735dc311a 100644
--- a/doc/HACKING/EndOfLifeTor.md
+++ b/doc/HACKING/EndOfLifeTor.md
@@ -1,12 +1,11 @@
-End of Life on an old release series
-------------------------------------
+# End of Life on an old release series
Here are the steps that the maintainer should take when an old Tor release
series reaches End of Life. Note that they are _only_ for entire series that
have reached their planned EOL: they do not apply to security-related
deprecations of individual versions.
-### 0. Preliminaries
+## 0. Preliminaries
0. A few months before End of Life:
Write a deprecation announcement.
@@ -16,7 +15,7 @@ deprecations of individual versions.
Send the announcement to tor-announce, tor-talk, tor-relays, and the
packagers.
-### 1. On the day
+## 1. On the day
1. Open tickets to remove the release from:
- the jenkins builds