Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #17449

Closed (moved)
(moved)
Open
Created Oct 29, 2015 by Georg Koppen@gk

Test bridges we ship in Tor Browser regularly

We should try to detect broken bridges we ship in Tor Browser early to minimize users trying them and to avoid overloading the remaining ones considerably/over a long period of time.

Not sure what "regularly" should mean in this context but I guess just testing them during our normal QA might not be enough as they could be down/unreachable temporarily.

We might set up something different maybe, even with a system that sends an email to the bridge operator (Cc'ing tor-assistants) after the bridge is repeatedly not usable.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking