Revise chutney download schedules for exponential backoff

Currently, chutney hard-codes most download schedules to "0, 5". This should be revised, probably after #20606 (moved) is implemented.

Split off #20597 (moved).

added component::core tor/chutney parent::20534 priority::medium resolution::wontfix severity::normal status::closed type::enhancement labels

We have to be careful with this, because those hard-coded schedules are still used for 0.2.8 and earlier in deterministic schedule mode.

0.2.7 is EOL, 0.2.8 will follow in 2018, but chutney still needs to work with 0.2.6 until its LTS expires in 2019.

Disowning tickets I don't intend to work on in the next 6 months.

Trac:
Owner: teor to N/A
Status: new to assigned

Mark all tickets that are assigned to nobody as "new".

Trac:
Status: assigned to new

We won't fix this ticket, the current solution seems to be working well enough.

Trac:
Resolution: N/A to wontfix
Status: new to closed

closed

moved to tpo/core/chutney#20607 (closed)