Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 833
    • Issues 833
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #25324
Closed
Open
Created Feb 21, 2018 by Nick Mathewson@nickm🏃Owner

Create a tor-releases.git repository.

This repository should be a fork of the main Tor repository, containing only the releases. In particular, it should have:

  • All supported tagged releases.
  • "release-0.x.y" branches that are updated whenever a release is tagged, and not otherwise.
  • "stable", "oldstable", "lts", and "alpha" branches that are updated whenever a release is tagged, and not otherwise. These branches may be force-pushed.
  • A "master" branch containing only a README file that tells you what branches to really use.

For background, see https://www.mail-archive.com/tor-dev@lists.torproject.org/msg10246.html and the surrounding thread.

We should also update doc/HACKING/ReleasingTor.md to describe this process.

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