Minor bandwidth file spec updates

The terminator was 4 characters long from sbws 0.1.0 to sbws 1.0.0

https://gitweb.torproject.org/torspec.git/tree/bandwidth-file-spec.txt#n96

changed milestone to %Tor: 0.4.1.x-final

added 041-proposed actualpoints::0.2 component::core tor/tor doc milestone::Tor: 0.4.1.x-final owner::teor points::0.2 priority::medium resolution::implemented reviewer::juga severity::normal status::closed tor-bwauth torspec type::defect labels

I'll do a bunch of minor changes in this ticket, in separate commits,

See my pull request: https://github.com/torproject/torspec/pull/51

Trac:
Summary: The terminator was 4 characters long from sbws 0.1.0 to sbws 1.0.0 to Minor bandwidth file spec updates
Status: assigned to needs_review
Description: https://gitweb.torproject.org/torspec.git/tree/bandwidth-file-spec.txt#n96

to

The terminator was 4 characters long from sbws 0.1.0 to sbws 1.0.0

https://gitweb.torproject.org/torspec.git/tree/bandwidth-file-spec.txt#n96

Trac:
Reviewer: N/A to juga

Mark some tickets as postfreeze-ok, to indicate that I think they are okay to accept in 0.4.0 post-freeze. Does not indicate that they are all necessary to do postfreeze.

Trac:
Keywords: N/A deleted, postfreeze-ok added

Looks good, i think there's a typo and i added a comment about the order of the headers.

Trac:
Status: needs_review to needs_revision

The typo was in the previous version.

I added a commit to fix the order.

Trac:
Keywords: postfreeze-ok deleted, 041-proposed added
Milestone: Tor: 0.4.0.x-final to Tor: 0.4.1.x-final
Points: N/A to 0.2
Actualpoints: N/A to 0.2
Status: needs_revision to needs_review

Replying to teor:

The typo was in the previous version.

ah, you're right, sorry.

I added a commit to fix the order.

LGTM. Though you might realize still more things to improve ;)

Trac:
Status: needs_review to merge_ready

Unparenting so I can close the other ticket.

Trac:
Parent: #29056 (closed) to N/A

One more fix: make it clear that Tor looks for a 5-character terminator.

I could have opened a separate ticket, but there would have been conflicts.

Trac:
Status: merge_ready to needs_review

LGTM.

Forgot to comment that i was using 76 characters per line cause that is what i saw in older specs, but we don't have documentation about it, so i guess there's no restriction.

Trac:
Status: needs_review to merge_ready

Merged!

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

closed

changed time estimate to 1h 36m

added 1h 36m of time spent

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