Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tor-browser-build
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 209
    • Issues 209
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • 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-build
  • Issues
  • #40141
Closed
Open
Created Nov 06, 2020 by Matthew Finkel@sysrqbMaintainer

Include release train in tag produced by signtag

Currently signtag outputs a tag as tbb-[% c("var/torbrowser_version") %]-[% c("var/torbrowser_build") %] (such as tbb-10.0.3-build1). Unfortunately, now we must tag two different branches for the same Tor Browser version number (desktop and Android). We could begin by including desktop and android in the tagname, such as tbb-10.0.4-desktop-build1 and tbb-10.0.4-android-build1, or we can use esr and rr (or something else similar) for indicating the ESR train or Rapid Release train because we will slowly move other platforms onto rapid release in the future. This results in tbb-10.0.4-esr-build1 and tbb-10.0.4-rr-build1.

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