Opened 2 years ago

Closed 18 months ago

#23118 closed defect (implemented)

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

Reported by: arma Owned by:
Priority: Medium Milestone: Tor: 0.3.3.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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.

Child Tickets

Change History (6)

comment:1 Changed 2 years ago by arma

Btw, I think Sina might not be doing recommendedversions anymore. According to
https://consensus-health.torproject.org/#recommendedversions
it is just weasel/arma/sebastian.

comment:2 Changed 2 years ago by arma

I opened #23119 for what I hope is a more thorough solution.

comment:3 Changed 2 years ago by arma

This bug was reported on irc several times, and also by Ralph on tor-relays:
https://lists.torproject.org/pipermail/tor-relays/2017-August/012715.html

comment:4 Changed 2 years ago by Sebastian

I've been waiting for the network team to get me some details about which versions they think should be recommended, and not updating anything in the meantime.

comment:5 Changed 22 months ago by nickm

Milestone: Tor: 0.3.3.x-final

comment:6 Changed 18 months ago by nickm

Resolution: implemented
Status: newclosed

73e5be5619ce39 fixes this, and also reminds people not to announce till the release is on the download page.

Note: See TracTickets for help on using tickets.