Make a Tor 0.2.7.7 release, with the patch for #20384
We sent out a patch for legacy/trac#20384 (moved), and apparently some groups like opensuse picked it up and did a package update on their side, but now we're in the unfortunate position of having some relays running 0.2.7.6 because they're buggy and old, and others running 0.2.7.6 because they updated to the patched package.
The smart thing on our side is probably to follow up with an actual release, with its own new version number and everything, which includes that patch plus the other things we've been wanting to backport (e.g. directory authority changes).
We have a release-0.2.7 branch which has a big pile of stuff merged into it from long ago. It is unlikely to now contain the set of things we would like in 0.2.7.7. But I bet it has some good suggestions.
Step one is to gather together the set of things we might want in 0.2.7.7 -- get the list from the current release-0.2.7 branch, and from trac tickets that have the backport-027 keyword, and... anywhere else we should be looking?
Step two is to pick the right subset of them for 0.2.7.7.
Then step three is to do the actual merging, and do up a changelog and release stanza, and put it out.
I can help with step two, but I think Sebastian and weasel can too (and I will be offline for a while starting in a few days, so best not to bottleneck on me anyway).
Who will get us through step one? :)
(And then once we've done an 0.2.7.7, we can think about an 0.2.6.11, and work our way back.)