diff options
| author | teor <teor@torproject.org> | 2020-04-03 22:02:11 +1000 |
|---|---|---|
| committer | teor <teor@torproject.org> | 2020-04-03 22:02:11 +1000 |
| commit | 0f10ddaa29366df56c63eeeb95e52c4a1fa71cd1 (patch) | |
| tree | 7138d63fe8e689901d9e8fb2ec23f4d796b596ba /doc | |
| parent | 0efcdb8918681763799b871b53785d77edbbf088 (diff) | |
| download | tor-0f10ddaa29366df56c63eeeb95e52c4a1fa71cd1.tar.gz tor-0f10ddaa29366df56c63eeeb95e52c4a1fa71cd1.zip | |
Re-apply: doc: Replace "underline" with "## Section name".
Re-applying changes after merge.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/HACKING/ReleaseSeriesLifecycle.md | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/doc/HACKING/ReleaseSeriesLifecycle.md b/doc/HACKING/ReleaseSeriesLifecycle.md index d0ce173336..4d223af18e 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: |