Skip to content

release checklist should include "make sure the new version got recommended"

In doc/HACKING/ReleasingTor.md we have

1. Get at least three of weasel/arma/Sebastian/Sina to put the new
   version number in their approved versions list.

But there's no follow-up step later in the checklist, to make sure that it really happened.

For Tor 0.3.0.10, it didn't happen -- moria1 recommended the new version, but nobody else did. So in retrospect, it would have been wise to do some sort of follow-up to check that the new version actually got recommended, before releasing.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information