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
  • #40013
Closed
Open
Created Jun 23, 2020 by Georg Koppen@gkDeveloper

Make sure we ship regular release builds with proper non-esr mozconfig files

Among other differences there are some tweaks in used mozconfig files and configurations that set regular release from esr release builds apart. We should make sure the mozconfig files we use for building Fenix reflect that.

We got reminded at that fact by looking closer at the fix that landed in https://bugzilla.mozilla.org/show_bug.cgi?id=1308251 and wondering whether MOZ_REQUIRE_SIGNING is set or not. It's not the case for the esr channel but it is set for regular release builds.

We should try to collect the differences and adjust the mozconfig files/build environment for non-esr builds accordingly where needed.

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