|
@@ -5,7 +5,7 @@ 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
|
|
@@ -18,7 +18,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
|
|
@@ -52,7 +52,7 @@ new Tor release:
|
|
|
memory leaks.)
|
|
|
|
|
|
|
|
|
-=== II. Write a changelog
|
|
|
+### II. Write a changelog
|
|
|
|
|
|
|
|
|
1a. (Alpha release variant)
|
|
@@ -139,7 +139,7 @@ new Tor release:
|
|
|
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
|
|
@@ -165,7 +165,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:
|
|
|
|
|
@@ -241,7 +241,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`
|