Re: [tor-bugs] #23118 [Core Tor/Tor]: release checklist should include "make sure the new version got recommended"

[Tor Bug Tracker & Wiki]

#23118: release checklist should include "make sure the new version got
recommended"
--+
 Reporter:  arma  |  Owner:  (none)
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  implemented
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  new => closed
 * resolution:   => implemented


Comment:

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

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #23118 [Core Tor/Tor]: release checklist should include "make sure the new version got recommended"

[Tor Bug Tracker & Wiki]

#23118: release checklist should include "make sure the new version got
recommended"
--+
 Reporter:  arma  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * milestone:   => Tor: 0.3.3.x-final


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #23118 [Core Tor/Tor]: release checklist should include "make sure the new version got recommended"

[Tor Bug Tracker & Wiki]

#23118: release checklist should include "make sure the new version got
recommended"
--+-
 Reporter:  arma  |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (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.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #23118 [Core Tor/Tor]: release checklist should include "make sure the new version got recommended"

[Tor Bug Tracker & Wiki]

#23118: release checklist should include "make sure the new version got
recommended"
--+-
 Reporter:  arma  |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (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

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #23118 [Core Tor/Tor]: release checklist should include "make sure the new version got recommended"

[Tor Bug Tracker & Wiki]

#23118: release checklist should include "make sure the new version got
recommended"
--+-
 Reporter:  arma  |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by arma):

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

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #23118 [Core Tor/Tor]: release checklist should include "make sure the new version got recommended"

[Tor Bug Tracker & Wiki]

#23118: release checklist should include "make sure the new version got
recommended"
--+-
 Reporter:  arma  |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (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.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #23118 [Core Tor/Tor]: release checklist should include "make sure the new version got recommended"

[Tor Bug Tracker & Wiki]

#23118: release checklist should include "make sure the new version got
recommended"
--+-
 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 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.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs