Add a format version number to the fallback file

atagar asked for this, and it's a good idea.

Let's use semantic versioning:

• major versions are for incompatible changes, like removing non-optional fields
• minor versions are for compatible changes, like adding fields
• patch versions are for bug fixes, like changing an incorrectly-formatted header comment

changed milestone to %Tor: 0.3.3.x-final

added component::core tor/fallback scripts fallback milestone::Tor: 0.3.3.x-final owner::teor parent::22271 points::0.2 priority::medium resolution::fixed review-group-28 reviewer::pastly severity::normal status::closed type::enhancement labels

I have merged all fallback format 2.0.0 changes into my branch fallback-format-2.

See fallback-format-2-v2, which also adds a delimiter at the end of every entry.

I squashed the original branch into fallback-format-2-v3 on https://github.com/teor2345/tor.git

Oops, this was meant to be in needs review with the other tickets on this branch. Sticking it in review-group-28, because they'll be reviewed together.

Trac:
Keywords: N/A deleted, review-group-28 added
Status: assigned to needs_review

Please see my revised branch fallback-format-2-v4 at https://github.com/teor2345/tor.git

pastly found some whitelist and blacklist changes from #22321 (moved) that I'd accidentally included in some commits, so I took them out.

Version number is added. LGTM, but make sure all fallback-format-2-v4 tickets are merge_ready.

Trac:
Status: needs_review to merge_ready

This code is now in my branch fallback-code-2018-01 at https://github.com/teor2345/tor.git

pastly reviewed all of these

Trac:
Reviewer: N/A to pastly

This branch has been merged, so these tickets are now implemented,

Trac:
Status: merge_ready to closed
Resolution: N/A to fixed

Remove useless Cc

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

closed

changed time estimate to 1h 36m

mentioned in issue #24742 (moved)

moved to tpo/core/fallback-scripts#24725 (closed)