Generate a new fallback list in 2018 and backport it to all supported versions

This is the actual list generation ticket.

changed milestone to %Tor: 0.2.9.x-final

added 029-backport 031-unreached-backport-maybe 032-unreached-backport-maybe 033-backport 034-backport 034-included-20180405 034-roadmap-subtask 034-triage-20180328 035-backport 035-can 035-roadmap-subtask 035-triaged-in-20180711 actualpoints::0.6 component::core tor/tor fallback milestone::Tor: 0.2.9.x-final owner::phoul parent::24786 points::1 priority::medium resolution::implemented s8-bootstrap severity::normal sponsor::8-can status::closed type::enhancement labels

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

The minimalist version of this is in-scope for 0.3.4.

Trac:
Keywords: 034-removed-20180328 deleted, 034-included-20180405 034-roadmap-subtask added

8/150 = 5% of fallbacks are currently down. https://consensus-health.torproject.org/graphs.html At this rate, it will be 2019 before we reach our 25% failure threshold. So we don't need to do a fallback rebuild in 0.3.4.

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

Trac:
Summary: Generate a new fallback list for 0.3.4 or 0.3.5 and backport it to all supported versions to Generate a new fallback list in 2018 and backport it to all supported versions

0.3.1 is end of life, there are no more backports. Tagging with 031-unreached-backport instead.

Trac:
Keywords: 034-included-20180405 034-roadmap-subtask deleted, 034-included-20180405, 031-unreached-backport, 034-roadmap-subtask added

0.3.1 is end of life, there are no more 0.3.1 maybe backports. Tagging with 031-unreached-backport-maybe.

Trac:
Keywords: 031-backport-maybe deleted, 031-unreached-backport-maybe added

Keywords does substrings in search, but not replace.

Trac:
Keywords: 031-unreached-backport deleted, N/A added

Trac:
Keywords: 031-unreached-backport-maybe deleted, 031-unreached-backport-maybe 035-roadmap-subtask added

Remove useless CC

Trac:
Cc: teor@torproject.org to N/A

Trac:
Keywords: 031-unreached-backport-maybe 035-roadmap-subtask deleted, 035-roadmap-subtask, 035-triaged-in-20180711, 031-unreached-backport-maybe added

Trac:
Milestone: Tor: 0.3.5.x-final to Tor: 0.3.6.x-final

25% of fallbacks are failing, so these tickets need to be done in 0.3.5.

Trac:
Milestone: Tor: 0.3.6.x-final to Tor: 0.3.5.x-final

Trac:
Keywords: N/A deleted, 035-can added

0.3.2 is end of life, so 032-backport is now 032-unreached-backport.

Trac:
Keywords: N/A deleted, 032-unreached-backport added

Tag 032-backport-maybe with 032-unreached-backport-maybe

Trac:
Keywords: 032-backport-maybe deleted, 032-unreached-backport-maybe added

Remove redundant 032-unreached-backport on 032-unreached-backport-maybe

Trac:
Keywords: 032-unreached-backport deleted, N/A added

Hi phoul,

Can you generate a fallback list from my branch ticket24838-24805 from https://github.com/teor2345/tor/ ?

It contains my fallback script changes from #24838 (moved), and your fallback whitelist changes from #24805 (moved).

Once you've created the list, you can attach it to this ticket, or put it in a branch.

I have also created a list using ticket24838-24805, it's in my branch ticket24803-029: https://github.com/torproject/tor/pull/571

Once you've done your list, I'll merge both lists, and update the changes file.

Trac:
Milestone: Tor: 0.3.5.x-final to Tor: 0.4.0.x-final
Sponsor: N/A to Sponsor8-can
Status: new to assigned
Owner: N/A to phoul
Actualpoints: N/A to 0.4
Keywords: N/A deleted, s8-bootstrap, 035-backport added