We should specify what is means for a Tor version to be obsolete
Atlas hit legacy/trac#24256 (moved) because our logic for what Tor versions are obsolete is opaque.
We should try to write it down somewhere better than the tor_version_is_obsolete() function. Maybe version-spec.txt is a good location?
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Roger Dingledine changed milestone to %Tor: 0.3.3.x-final in legacy/trac
changed milestone to %Tor: 0.3.3.x-final in legacy/trac
- Roger Dingledine added component::core tor/tor in Legacy / Trac milestone::Tor: 0.3.3.x-final in Legacy / Trac priority::medium in Legacy / Trac resolution::implemented in Legacy / Trac review-group-31 in Legacy / Trac reviewer::dgoulet in Legacy / Trac severity::normal in Legacy / Trac status::closed in Legacy / Trac tor-spec in Legacy / Trac type::defect in Legacy / Trac labels
added component::core tor/tor in Legacy / Trac milestone::Tor: 0.3.3.x-final in Legacy / Trac priority::medium in Legacy / Trac resolution::implemented in Legacy / Trac review-group-31 in Legacy / Trac reviewer::dgoulet in Legacy / Trac severity::normal in Legacy / Trac status::closed in Legacy / Trac tor-spec in Legacy / Trac type::defect in Legacy / Trac labels
- Owner
Trac:
Milestone: N/A to Tor: 0.3.3.x-final - Owner
I've tried to do this with
ticket24257
in my public torspec repository. Please review?Trac:
Status: new to needs_review - Owner
Trac:
Keywords: N/A deleted, review-group-31 added - Owner
-
[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.
- Double white space at the end of the commit.
Trac:
Reviewer: N/A to dgoulet
Keywords: N/A deleted, tor-spec added
Status: needs_review to needs_revision -
- Owner
Replying to 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 legacy/trac#24023 (moved) though. I'll fix it.
- Double white space at the end of the commit.
Merging and fixing that too.
Thanks!
Trac:
Resolution: N/A to implemented
Status: needs_revision to closed -
- Trac closed
closed
- Trac moved from legacy/trac#24257 (moved)
moved from legacy/trac#24257 (moved)
- Trac added Specifications label and removed 1 deleted label
added Specifications label and removed 1 deleted label