Form a plan for killing off client versions which assume they'll live forever

[teor]

From at least 0.2.4 to 0.2.6, tor client versions assume that they will keep on using the network forever. They have no "request to stop" code or other mechanisms that prevent them becoming a drain on the network.

It would help to plan their transition out at some point, so we can work out what to do to make version obsolescence in future.

See #15233 for killing off 0.2.2 and 0.2.3

[nickm]

Bulk-replace SponsorU keyword with SponsorU field.

[nickm]

These two tickets (#15940 and #15941) are design-only, and should get solved when we finalize the associated design proposals (264 and 266).

[nickm]

We have design proposals here, but not finalized. Need to take another look in 0.2.9

[teor]

Actually 0.2.9.

[nickm]

Put all unowned "assigned" tickets back into "new".

[teor]

Milestone renamed

[nickm]

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

[nickm]

Remove an old triaging keyword.

[dgoulet]

I don't think we will or can do this in 033.

[nickm]

Per our triage process, these tickets are pending removal from 0.3.4.

[nickm]

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

[nickm]

I am not actually working on these tickets, so they shouldn't be assigned to me.

[teor]

Change tickets that are assigned to nobody to "new".