Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #3223

Closed (moved)
Open
Opened May 18, 2011 by Roger Dingledine@arma

bridgedb's reserved bridge emails should annotate bridges by stability

Right now in the emails that bridgedb sends out for its reserved bridges, the order of bridges seems pretty arbitrary. My guess is that it's based on whatever order they appear in the db.

Once we've sent out 10 days worth of bridges though, some of these bridges have been in the "Bridges still RUNNING since the last email I sent you:" list for all 10 of those days. We should make it clearer which ones are stable.

One approach would be to annotate the address like

128.31.0.34:9101    (8 days at this address)

and then sort the bridges by stability in the email we send.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#3223