Update dir-spec for "reasonably live" consensuses

In networkstatus_get_reasonably_live_consensus() and check_expired_networkstatus_callback(), tor has the concept of a "reasonably live" consensus. A consensus is reasonably live if it expired less than 24 hours ago.

This isn't in the directory spec, should it be?

changed milestone to %Tor: 0.3.2.x-final

added component::core tor/tor doc milestone::Tor: 0.3.2.x-final owner::nickm points::.1 priority::low resolution::implemented severity::normal status::closed tor-spec type::defect labels

Trac:
Priority: Medium to Low

Throw most 0.2.8 "NEW" tickets into 0.2.9. I expect that many of them will subsequently get triaged out.

Trac:
Milestone: Tor: 0.2.8.x-final to Tor: 0.2.9.x-final

Trac:
Points: N/A to very small
Reviewer: N/A to N/A

Trac:
Points: very small to .1

Trac:
Keywords: tor-spec doc deleted, doc, isaremoved, tor-spec added
Milestone: Tor: 0.2.9.x-final to Tor: 0.2.???

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

Trac:
Keywords: N/A deleted, tor-03-unspecified-201612 added
Milestone: Tor: 0.3.??? to Tor: unspecified

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

Trac:
Keywords: isaremoved deleted, N/A added

Trac:
Owner: N/A to nickm
Status: new to accepted
Milestone: Tor: unspecified to Tor: 0.3.2.x-final

Done in 85d7c57bbdf549.

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

closed

changed time estimate to 48m

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