[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #28731 [Core Tor/Tor]: log bootstrap tag name for easier troubleshooting
#28731: log bootstrap tag name for easier troubleshooting
-------------------------------------------------+-------------------------
Reporter: catalyst | Owner:
| catalyst
Type: defect | Status:
| merge_ready
Priority: Medium | Milestone: Tor:
| 0.3.4.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: s8-bootstrap, 033-backport-maybe, | Actual Points:
034-backport-maybe, 035-backport-maybe |
Parent ID: #28018 | Points: 0.1
Reviewer: | Sponsor:
| Sponsor8-can
-------------------------------------------------+-------------------------
Comment (by atagar):
Hi Nick. Stem had a release just a few weeks ago and
[https://stem.torproject.org/change_log.html generally accumulates enough
changes] to warrant another release annually.
I cautioned above that this will make folks sad. I see three options
here...
1. Revert or punt this tor commit for a year. Stem aside, personally I
don't understand why this change is desirable. That said, once we have
DROPOWNERSHIP and Stem 1.8 is out I won't care what modifications you make
to the bootstrap messages.
2. Release a Stem 1.7.1 hotfix release. This creates work for our
packaging community and I avoid it unless there's a critical bug, but if
this logging change is really important to you we can go this route.
3. Continue as-is and break callers of launch_tor(). This is the route the
network team seemed to prefer on this ticket.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28731#comment:16>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs