commit 0f10ddaa29366df56c63eeeb95e52c4a1fa71cd1 Author: teor <teor@torproject.org> Date: Fri Apr 3 22:02:11 2020 +1000 Re-apply: doc: Replace "underline" with "## Section name". Re-applying changes after merge. --- doc/HACKING/ReleaseSeriesLifecycle.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/doc/HACKING/ReleaseSeriesLifecycle.md b/doc/HACKING/ReleaseSeriesLifecycle.md index d0ce17333..4d223af18 100644 --- a/doc/HACKING/ReleaseSeriesLifecycle.md +++ b/doc/HACKING/ReleaseSeriesLifecycle.md @@ -1,13 +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 an entire series that has reached its planned EOL: they do not apply to security-related deprecations of individual versions. + ### 1. Preliminaries 1. A few months before End of Life: @@ -18,6 +16,7 @@ deprecations of individual versions. Send the announcement to tor-announce, tor-talk, tor-relays, and the packagers. + ### 2. On the day 1. Open tickets to remove the release from: