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

added 034-removed-20180328 034-triage-20180328 SponsorS component::core tor/tor milestone::Tor: unspecified points::3 priority::high severity::normal status::new tor-dos-designs type::task 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 (#15940 (moved) and #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.???

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

Trac:
Keywords: N/A deleted, tor-03-unspecified-201612 added
Milestone: Tor: 0.3.??? to Tor: unspecified

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

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

Trac:
Owner: N/A to nickm
Milestone: Tor: unspecified to Tor: 0.3.2.x-final
Status: new to accepted

Trac:
Sponsor: N/A to SponsorV-can

Trac:
Milestone: Tor: 0.3.2.x-final to Tor: 0.3.3.x-final

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

Trac:
Milestone: Tor: 0.3.3.x-final to Tor: 0.3.4.x-final

Trac:
Keywords: N/A deleted, 034-triage-20180328 added

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

Trac:
Keywords: N/A deleted, 034-removed-20180328 added

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

Trac:
Milestone: Tor: 0.3.4.x-final to Tor: unspecified

Removing sponsor V as we do not have more time to include this tickets in the sponsor.

Removing sponsor from tickets that we do not have time to fit in the remain of this sponsorship.

Trac:
Sponsor: SponsorV-can to N/A

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

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

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

Trac:
Status: assigned to new

changed time estimate to 24h

mentioned in issue #15941 (moved)

mentioned in issue #15942 (moved)

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