[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #1602 [Metrics]: TorStatus should use Tordnsel instead of its own

#1602: TorStatus should use Tordnsel instead of its own
----------------------------+-----------------------------------------------
        Reporter:  phobos   |        Owner:  karsten              
            Type:  task     |       Status:  reopened             
        Priority:  normal   |    Milestone:  Tor Status Deployment
       Component:  Metrics  |      Version:                       
      Resolution:           |     Keywords:                       
          Parent:           |       Points:                       
Actualpointsdone:           |   Pointsdone:                       
    Actualpoints:           |  
----------------------------+-----------------------------------------------

Comment(by karsten):

 Well, I don't think our Trac is the right place to hold !TorStatus bugs,
 because we don't maintain !TorStatus.  But I wouldn't mind making a new
 component and re-assigning the tickets.  What I do mind about is having
 them assigned to the Metrics component and to me, because there's no way
 for me to make progress and solve these tickets.

 Shall I create a component and re-assign the tickets?

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1602#comment:4>
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