Opened 3 years ago

Closed 3 years ago

#20914 closed enhancement (implemented)

Consider switching to 3 fallbacks per operator

Reported by: teor Owned by: teor
Priority: Medium Milestone:
Component: Core Tor/Fallback Scripts Version:
Severity: Normal Keywords: fallback
Cc: Actual Points:
Parent ID: #18828 Points:
Reviewer: Sponsor:

Description

It gets us 173 fallbacks, rather than 155.

Child Tickets

Attachments (2)

op3_fallbacks (18.0 KB) - added by teor 3 years ago.
Fallback list with 3 fallbacks per operator
op3_fallbacks.log (513.8 KB) - added by teor 3 years ago.
Fallback selection log with 3 fallbacks per operator

Download all attachments as: .zip

Change History (7)

Changed 3 years ago by teor

Attachment: op3_fallbacks added

Fallback list with 3 fallbacks per operator

Changed 3 years ago by teor

Attachment: op3_fallbacks.log added

Fallback selection log with 3 fallbacks per operator

comment:1 Changed 3 years ago by teor

I want to send out this draft list to tor-relays and CC all the operators.
But I think I will wait until the weekend, collate all the replies, rebuild the list, and then send the email out.

comment:2 Changed 3 years ago by teor

And I want to remind operators that this time, we are taking 3 per operator.

comment:3 Changed 3 years ago by nickm

Component: Core Tor/TorCore Tor/Fallback Scripts
Milestone: Tor: 0.3.0.x-final
Owner: set to teor

Batch-move updateFallbackDirs.py tickets into a new component, and remove them from maint-0.3.0.

I'm doing this as a separate component, after discussion with teor, mainly because development here seems to be decoupled from development on tor itself: they don't need to have the same release schedules, for example.

comment:4 Changed 3 years ago by nickm

Merged teor/fallbacks-20161219, which included a patch for this.

comment:5 Changed 3 years ago by nickm

Resolution: implemented
Status: newclosed
Note: See TracTickets for help on using tickets.