Make a standard transition plan for killing off a client version

Parent ticket for transitioning current and future client versions off the tor network with a minimal amount of pain.

changed milestone to %Tor: unspecified in legacy/trac

added 034-removed-20180328 in Legacy / Trac 034-triage-20180328 in Legacy / Trac SponsorS in Legacy / Trac component::core tor/tor in Legacy / Trac milestone::Tor: unspecified in Legacy / Trac points::3 in Legacy / Trac priority::high in Legacy / Trac severity::normal in Legacy / Trac status::new in Legacy / Trac tor-dos-designs in Legacy / Trac type::task in Legacy / Trac labels

Make title clearer

Trac:
Summary: Make transition plans for current and future obsolete client versions to Make a standard transition plan for killing off a client version

Trac:
Type: defect to task

Trac:
Sponsor: N/A to N/A
Milestone: Tor: 0.2.??? to Tor: 0.2.8.x-final

Bulk-replace SponsorU keyword with SponsorU field.

Trac:
Sponsor: N/A to SponsorU
Keywords: SponsorU deleted, N/A added

Trac:
Points: N/A to medium

Trac:
Priority: Medium to High

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

Trac:
Status: new to accepted
Owner: N/A to nickm

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

Trac:
Milestone: Tor: 0.2.8.x-final to Chronos: phase two

Actually 0.2.9.

Trac:
Severity: N/A to Normal
Reviewer: N/A to N/A
Milestone: Chronos: phase two to Tor: 0.2.9.x-final

Trac:
Sponsor: SponsorU to SponsorU-can

Trac:
Keywords: N/A deleted, tor-dos-designs added

Trac:
Points: medium to 3

Trac:
Status: accepted to assigned
Owner: nickm to N/A

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

Trac:
Status: assigned to new

Trac:
Sponsor: SponsorU-can to N/A

Trac:
Milestone: Tor: 0.2.9.x-final to Tor: 0.2.???

Trac:
Keywords: N/A deleted, 029-OUT added

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???