Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Tor Browser
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,003
    • Issues 1,003
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • Tor Browser
  • Issues
  • #40070
Closed
Open
Created Aug 03, 2020 by Matthew Finkel@sysrqbMaintainer3 of 3 tasks completed3/3 tasks

Use Tor Browser 10.5 as a watershed update

In #40042 (closed) @mcs raised the question about whether we need a watershed update before migrating to 78esr. We decided that wasn't needed, but we may want a watershed update for Tor Browser that would allow simplifying some of our implementations.

Some of the code areas that could be simplified described in that ticket. Let's continue investigating it here, and we should create individual tickets for each component that needs changes.

  • #40042 (closed)
  • tor-launcher#28044 (closed)
  • #40137 (closed)

(I'm not sure how we can best document this, so I'm beginning with ticket numbers)

Edited Dec 07, 2021 by Georg Koppen
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking