#27735: Tors with cached consensuses can't upgrade to a version that stops
supporting a required protocol
-------------------------------------------------+-------------------------
 Reporter:  teor                                 |          Owner:  nickm
     Type:  defect                               |         Status:
                                                 |  needs_review
 Priority:  High                                 |      Milestone:  Tor:
                                                 |  0.4.0.x-final
Component:  Core Tor/Tor                         |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  029-backport-maybe, 033-backport-    |  Actual Points:  .3
  maybe, 034-backport-maybe, 032-unreached-      |
  backport-maybe, prop297                        |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------
Changes (by nickm):

 * keywords:
     029-backport-maybe, 033-backport-maybe, 034-backport-maybe, 032
     -unreached-backport-maybe
     =>
     029-backport-maybe, 033-backport-maybe, 034-backport-maybe, 032
     -unreached-backport-maybe, prop297
 * status:  accepted => needs_review
 * actualpoints:   => .3


Comment:

 See branch `prop297`, PR at https://github.com/torproject/tor/pull/541 .

 This code updates the update_versions script to automatically keep the
 version dates moving forward with each release.  (It also rewrites
 update_versions in Python, to be less horrible.)

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27735#comment:9>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Reply via email to