[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #24257 [Core Tor/Tor]: We should specify what is means for a Tor version to be obsolete

#24257: We should specify what is means for a Tor version to be obsolete
---------------------------------------+-----------------------------------
 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:  review-group-31, tor-spec  |  Actual Points:
Parent ID:                             |         Points:
 Reviewer:  dgoulet                    |        Sponsor:
---------------------------------------+-----------------------------------
Changes (by nickm):

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


Comment:

 Replying to [comment:4 dgoulet]:
 > * `[Will become mandatory.]` when... ? Like when we decide or there is a
 date or when which ticket is resolved?
 >
 >  Considering this comment, I think we can deduce a date no?
 >
 > {{{
 > +       This field was first added in Tor 0.2.9.x. Some time after all
 earlier
 > +       Tor relay versions are obsolete, it will become mandatory.
 > }}}

 I think this was in #24023 though.  I'll fix it.

 > * Double white space at the end of the commit.

 Merging and fixing that too.

 Thanks!

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24257#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs