New guard plan - update guard state when a circuit fails/succeeds

New guard plan summarized at https://lists.torproject.org/pipermail/tor-dev/2016-July/011234.html

6. Update guard state when a circuit fails/succeeds

• Section ON_FAIL and ON_SUCCESS
• See entry_guard_register_connect_status()
• Unittest

changed milestone to %Tor: 0.3.0.x-final

added TorCoreTeam201611 component::core tor/tor isaremoved milestone::Tor: 0.3.0.x-final nickm-deferred-20161005 nickwants029 owner::nickm parent::19877 points::3 priority::medium resolution::implemented severity::normal sponsor::U-must status::closed tor-guards-revamp type::task version::tor unspecified labels

Trac:
Milestone: Tor: 0.2.9.x-final to Tor: 0.2.???
Keywords: N/A deleted, isaremoved added

Batch modification: I believe these are all (or nearly all!) required for the successful completion of the SponorU guards task.

Trac:
Keywords: N/A deleted, nickwants029, tor-guards-revamp added

Trac:
Cc: N/A to asn

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.2.9.x-final
Sponsor: SponsorU to SponsorU-must

Deferring more things -- even ones I love -- to 0.3.0. Please argue if I'm wrong.

Trac:
Keywords: N/A deleted, nickm-deferred-20161005 added
Milestone: Tor: 0.2.9.x-final to Tor: 0.3.0.x-final

Reassigning some prop 271 tickets to nickm for parallel work in Oct.

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

The backend for this is now in my (much-rebased, very unstable) prop271 branch (called prop271-wip). But it isn't tied together yet.

Trac:
Keywords: N/A deleted, TorCoreTeam201611 added

(batch change): These are now done in my prop271-wip branch.

Trac:
Resolution: N/A to implemented
Status: assigned to closed

closed

changed time estimate to 24h

moved to tpo/core/tor#19882 (closed)