Stop listing relays that run Tor 0.2.2

We haven't recommended the version for about a month now. Time to stop accepting servers running it.

changed milestone to %Tor: 0.2.5.x-final

added 025-triaged component::core tor/tor milestone::Tor: 0.2.5.x-final parent::9476 priority::medium resolution::implemented status::closed type::defect labels

Branch "ticket11149" in my public repository does this in the obvious way.

(0.2.2 relays are down to 2.5% by bandwidth and 4.7% by number. They should all been getting warnings to upgrade for a month now.)

Trac:
Status: new to needs_review

Trac:
Keywords: N/A deleted, 025-triaged added

Trac:
Summary: Add 0.2.2 to list of versions we don't accept in the consensus to Stop listing relays that run Tor 0.2.2

arma and weasel don't object; let's pull the trigger after 0.2.5.3-alpha is out.

I did a pass through the consensus to find relays with old versions and working contact info and consensus weights >= 100, to let them know to upgrade.

There are a handful of very fast relays with old versions and no contact info.

Looking at things as a percentage of the network is not the whole picture, since 4.7% of 5121 is still 240 volunteers that we are effectively telling to go shove it. As the network grows, the number of real volunteers grows too.

But all of that said, I recognize that keeping relay versions sufficiently up-to-date is necessary too. Hopefully some of them will upgrade.

Merged.

Trac:
Resolution: N/A to implemented
Status: needs_review to closed

Are we sure we want to cut out 0.2.3.x for x<25 also? The consensus currently still recommends 0.2.3.24-rc so I think we will want to be more lenient here.

Looking over the changelog, I think 0.2.3.16-alpha's fix of #6033 (moved) makes that one a plausible "not below this one" cutoff. Other ideas for cutoffs?

I put that in place for now while we see if there's more to discuss.

(Roger's commit was ddaeb4deee7b2a7772baac9a09abc54b689d8437)

closed

mentioned in issue #11243 (moved)

moved to tpo/core/tor#11149 (closed)