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
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

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
  • #30447

Closed (moved)
Open
Opened May 09, 2019 by emma peel@emmapeel

TBA strings are coming from a different branch each release, which makes it difficult to track in transifex

Most of the resources we have in Transifex are linked to source files we have on our own repositories, so when we make changes on our repositories, those changes appear automatically in Transifex. This happens with all Torbutton strings, coming mostly from the torbutton.git repository.

But the strings for Tor Browser for Android come from the Tor Browser repository, and the branch name is not 'master' but it is the release name, as in current branch is 'tor-browser-60.6.1esr-8.5-1'

This makes it impossible to track permanently the branch, somebody needs to login to transifex with enough privileges to change the autoupdate to the new URL, or do updates as part of the release cycle with the push feature of the tx client ( https://docs.transifex.com/client/push )

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#30447