diff options
| author | Bartosz Duszel <bartosz.duszel@protonmail.com> | 2020-03-22 13:50:58 +0100 |
|---|---|---|
| committer | Bartosz Duszel <bartosz.duszel@protonmail.com> | 2020-03-22 13:50:58 +0100 |
| commit | fd6a35eb59f1d8bce6afc773d0c44937326e0034 (patch) | |
| tree | 5b2f0d92fc15fa9b99dfb716fed9344dd4f60776 /doc/HACKING/ReleasingTor.md | |
| parent | dccac40e6998a63894823c0ca3f8ea9c21ef8f18 (diff) | |
| download | tor-fd6a35eb59f1d8bce6afc773d0c44937326e0034.tar.gz tor-fd6a35eb59f1d8bce6afc773d0c44937326e0034.zip | |
Update README files with common style.
- external links use markdown's []() format,
- local files are formated with backquotes,
- duplicated new lines were removed,
- unnecesary single spaces were removed,
- broken links and local paths were updated.
Diffstat (limited to 'doc/HACKING/ReleasingTor.md')
| -rw-r--r-- | doc/HACKING/ReleasingTor.md | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/doc/HACKING/ReleasingTor.md b/doc/HACKING/ReleasingTor.md index 0f453ca2aa..fbc5de54eb 100644 --- a/doc/HACKING/ReleasingTor.md +++ b/doc/HACKING/ReleasingTor.md @@ -1,4 +1,3 @@ - Putting out a new release ------------------------- @@ -51,10 +50,8 @@ new Tor release: libevent and openssl, so using valgrind will sometimes find extra memory leaks.) - ### II. Write a changelog - 1a. (Alpha release variant) Gather the `changes/*` files into a changelog entry, rewriting many @@ -138,7 +135,6 @@ 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. 1. In `maint-0.?.x`, bump the version number in `configure.ac` and run @@ -215,7 +211,6 @@ new Tor release: Include a link to the changelog. - 4. Add the version number to Trac. To do this, go to Trac, log in, select "Admin" near the top of the screen, then select "Versions" from the menu on the left. At the right, there will be an "Add version" |