|
|
= How to put out a version of Tor =
|
|
|
|
|
|
Here's Roger's release process, as written up in mid-2010.
|
|
|
|
|
|
1. use it for a while. see if it has any bugs where every single user who tries it is going to report the bug. resolve those.
|
|
|
1. gather the changes/* files into a changelog entry, rewriting many of them and reordering to focus on what users and funders would find interesting and understandable.
|
|
|
1. bump the version number
|
|
|
1. make dist, tell #tor about the tarball and see if anybody has problems building it.
|
|
|
1. get at least two of weasel/arma/karsten to put the new version number in the approved versions list.
|
|
|
1. sign and push the tarball, sign and push the tag
|
|
|
1. edit include/versions.wmi to note the new version, rebuild and push the website
|
|
|
1. optionally, tell andrew and helix that a new tarball is up
|
|
|
1. After a few days, or sometimes longer depending on what packages we're still waiting for, compose a short release blurb to highlight the user-facing changes, and send it to or-talk. Insert said release blurb into the ChangeLog stanza too.
|
|
|
|