diff options
| author | Bartosz Duszel <bartosz.duszel@protonmail.com> | 2020-03-26 16:19:42 +0100 |
|---|---|---|
| committer | Bartosz Duszel <bartosz.duszel@protonmail.com> | 2020-03-26 16:19:42 +0100 |
| commit | b210aefb7fd22e49077f7be6ef481ca0bf20d2bb (patch) | |
| tree | f349bb124418a45747e958bb86fbd8d25308799d /doc/HACKING/ReleasingTor.md | |
| parent | af4b5eba34f372376d78abc261e7043467e15613 (diff) | |
| download | tor-b210aefb7fd22e49077f7be6ef481ca0bf20d2bb.tar.gz tor-b210aefb7fd22e49077f7be6ef481ca0bf20d2bb.zip | |
doc: Replace "underline" with "## Section name".
This approach doesn't require variable-length underlines.
Diffstat (limited to 'doc/HACKING/ReleasingTor.md')
| -rw-r--r-- | doc/HACKING/ReleasingTor.md | 15 |
1 files changed, 7 insertions, 8 deletions
diff --git a/doc/HACKING/ReleasingTor.md b/doc/HACKING/ReleasingTor.md index fbc5de54eb..2464d8afb4 100644 --- a/doc/HACKING/ReleasingTor.md +++ b/doc/HACKING/ReleasingTor.md @@ -1,10 +1,9 @@ -Putting out a new release -------------------------- +# Putting out a new release Here are the steps that the maintainer should take when putting out a new Tor release: -### 0. Preliminaries +## 0. Preliminaries 1. Get at least two of weasel/arma/Sebastian to put the new version number in their approved versions list. Give them a few @@ -17,7 +16,7 @@ new Tor release: date of a TB that contains it. See note below in "commit, upload, announce". -### I. Make sure it works +## I. Make sure it works 1. Make sure that CI passes: have a look at Travis (https://travis-ci.org/torproject/tor/branches), Appveyor @@ -50,7 +49,7 @@ new Tor release: libevent and openssl, so using valgrind will sometimes find extra memory leaks.) -### II. Write a changelog +## II. Write a changelog 1a. (Alpha release variant) @@ -135,7 +134,7 @@ new Tor release: to start sorting and condensing entries. (Generally, we don't edit the text of existing entries, though.) -### III. Making the source release. +## III. Making the source release. 1. In `maint-0.?.x`, bump the version number in `configure.ac` and run `make update-versions` to update version numbers in other @@ -161,7 +160,7 @@ new Tor release: If it is not, you'll need to poke Roger, Weasel, and Sebastian again: see item 0.1 at the start of this document. -### IV. Commit, upload, announce +## IV. Commit, upload, announce 1. Sign the tarball, then sign and push the git tag: @@ -236,7 +235,7 @@ new Tor release: For templates to use when announcing, see: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/AnnouncementTemplates -### V. Aftermath and cleanup +## V. Aftermath and cleanup 1. If it's a stable release, bump the version number in the `maint-x.y.z` branch to "newversion-dev", and do a `merge -s ours` |