Opened 4 years ago

Last modified 12 months ago

#15940 accepted task

Make a standard transition plan for killing off a client version

Reported by: teor Owned by: nickm
Priority: High Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: SponsorS, tor-dos-designs, 034-triage-20180328, 034-removed-20180328
Cc: nickm Actual Points:
Parent ID: Points: 3
Reviewer: Sponsor: SponsorV-can

Description

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

Child Tickets

TicketStatusOwnerSummaryComponent
#15935closedImplement an advisory-only request to stop for old clientsCore Tor/Tor
#15941acceptednickmForm a plan for killing off client versions which assume they'll live foreverCore Tor/Tor

Change History (28)

comment:1 Changed 4 years ago by teor

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

Make title clearer

comment:2 Changed 4 years ago by teor

Type: defecttask

comment:3 Changed 3 years ago by nickm

Milestone: Tor: 0.2.???Tor: 0.2.8.x-final

comment:4 Changed 3 years ago by nickm

Keywords: SponsorU removed
Sponsor: SponsorU

Bulk-replace SponsorU keyword with SponsorU field.

comment:5 Changed 3 years ago by nickm

Points: medium

comment:6 Changed 3 years ago by nickm

Priority: MediumHigh

comment:7 Changed 3 years ago by nickm

Owner: set to nickm
Status: newaccepted

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

comment:8 Changed 3 years ago by nickm

Milestone: Tor: 0.2.8.x-finalChronos: phase two

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

comment:9 Changed 3 years ago by teor

Milestone: Chronos: phase twoTor: 0.2.9.x-final
Severity: Normal

Actually 0.2.9.

comment:10 Changed 3 years ago by isabela

Sponsor: SponsorUSponsorU-can

comment:11 Changed 3 years ago by nickm

Keywords: tor-dos-designs added

comment:12 Changed 3 years ago by isabela

Points: medium3

comment:13 Changed 3 years ago by nickm

Owner: nickm deleted
Status: acceptedassigned

comment:14 Changed 3 years ago by nickm

Status: assignednew

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

comment:15 Changed 3 years ago by nickm

Sponsor: SponsorU-can

comment:16 Changed 3 years ago by isabela

Milestone: Tor: 0.2.9.x-finalTor: 0.2.???

comment:17 Changed 3 years ago by isabela

Keywords: 029-OUT added

comment:18 Changed 2 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:19 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

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

comment:20 Changed 22 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:21 Changed 22 months ago by nickm

Keywords: 029-OUT removed

comment:22 Changed 21 months ago by nickm

Milestone: Tor: unspecifiedTor: 0.3.2.x-final
Owner: set to nickm
Status: newaccepted

comment:23 Changed 21 months ago by nickm

Sponsor: SponsorV-can

comment:24 Changed 19 months ago by nickm

Milestone: Tor: 0.3.2.x-finalTor: 0.3.3.x-final

comment:25 Changed 13 months ago by dgoulet

Milestone: Tor: 0.3.3.x-finalTor: 0.3.4.x-final

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

comment:26 Changed 12 months ago by nickm

Keywords: 034-triage-20180328 added

comment:27 Changed 12 months ago by nickm

Keywords: 034-removed-20180328 added

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

comment:28 Changed 12 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: unspecified

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

Note: See TracTickets for help on using tickets.