#23118: release checklist should include "make sure the new version got
     Reporter:  arma          |      Owner:
         Type:  defect        |     Status:  new
     Priority:  Medium        |  Milestone:
    Component:  Core Tor/Tor  |    Version:
     Severity:  Normal        |   Keywords:
Actual Points:                |  Parent ID:
       Points:                |   Reviewer:
      Sponsor:                |
 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, 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.

Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23118>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
tor-bugs mailing list

Reply via email to