[tor-bugs] #28925 [Core Tor/Tor]: distinguish PT vs proxy for real in bootstrap tracker

[Tor Bug Tracker & Wiki]

#28925: distinguish PT vs proxy for real in bootstrap tracker
-------------------------------------------------+-------------------------
 Reporter:  catalyst                             |          Owner:
                                                 |  catalyst
     Type:  defect                               |         Status:
                                                 |  merge_ready
 Priority:  High                                 |      Milestone:  Tor:
                                                 |  0.4.0.x-final
Component:  Core Tor/Tor                         |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  asn-merge, teor-merge,               |  Actual Points:  2
  s8-bootstrap, usability, ux, tor-pt, tbb-      |
  needs, 040-must, network-team-                 |
  roadmap-2019-Q1Q2                              |
Parent ID:  #28018                               |         Points:
 Reviewer:  nickm                                |        Sponsor:
                                                 |  Sponsor19
-------------------------------------------------+-------------------------

Comment (by teor):

 Squashed as bug28925_040_squashed at
 https://github.com/torproject/tor/pull/836
 Master merge is bug28925_master_squashed at
 https://github.com/torproject/tor/pull/837

 I've read the code comments and warnings from practracker. I think I need
 to update the practracker exceptions file in a separate commit.

 I've updated the merge policy to include a "wait for master and
 practracker" step:
 https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/MergePolicy?action=diff&version=9

 Longer-term, we should think about how to improve the ergonomics of
 practracker:
 1. If we push and build master first, then we'll catch practracker errors
 early, see #29879.
 2. If we write a script to update exceptions and merge forward, then we'll
 be able to handle exceptions in backport branches faster and more
 reliably, see #29880. We don't need to make this change until we split off
 an 0.4.2 branch.

 But I'm not sure how to discover practracker errors in backport branches.
 We could require master merges for every backport branch. I wonder if
 there is a way to automate that? I opened #29881 to see if we could make a
 bot.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28925#comment:20>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online