Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #32498

Closed (moved)
Open
Created Nov 14, 2019 by boklm@boklm

Consider updating MAR_CHANNEL_ID for nightly build (and maybe alpha too)

In browser/confvars.sh (from tor-browser.git) we currently set MAR_CHANNEL_ID to torbrowser-torproject-release in all cases.

I see that Mozilla is using a different MAR_CHANNEL_ID for each of their channel (previously by updating browser/confvars.sh, and now by setting it from taskcluster: https://hg.mozilla.org/releases/mozilla-release/rev/66f52bda7e14e26235bd0a43bb68ad11775046e4).

So I am wondering if we should do the same, and use a different MAR_CHANNEL_ID for nightly, and maybe for the alpha too.

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