commit 5580fbb0c481a1f52fcef9e5b65966d5a91446d9 Author: Sebastian Hahn <sebastian@torproject.org> Date: Thu Jul 14 13:03:55 2011 +0200 Update HACKING with some more release instructions --- doc/HACKING | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-) diff --git a/doc/HACKING b/doc/HACKING index feeb05d..9747f22 100644 --- a/doc/HACKING +++ b/doc/HACKING @@ -495,7 +495,11 @@ box. By convention, we enter the version in the form "Tor: 0.2.2.23-alpha" (or whatever the version is), and we select the date as the date in the ChangeLog. -11) Wait up to a day or two (for a development release), or until most +11) Forward-port the ChangeLog. + +12) Update the topic in #tor to reflect the new version. + +12) Wait up to a day or two (for a development release), or until most packages are up (for a stable release), and mail the release blurb and changelog to tor-talk or tor-announce.