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,285
    • Issues 1,285
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 6
    • Merge requests 6
  • 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
  • #16632

Closed
Open
Created Jul 21, 2015 by Mike Perry@mikeperryDeveloper

Turn on the background autoupdater

Now that we're fairly sure that everything is working OK with our offline mar signing, etc, we should turn on the background updater for 5.0. The current popup for updates is still a barrier for some people to update immediately, I suspect.

I will test an upgrade from 5.0a2 to 5.0a3 with app.update.auto set to true on Linux, so we can verify it still works across the FF31 to FF38 transition. If that works out, we should set the pref by default in 5.0a4, and again in 5.0.

I might need someone else to test Windows and Mac.

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