Opened 19 months ago

Last modified 14 months ago

#25324 new defect

Create a tor-releases.git repository.

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


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 and the surrounding thread.

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

Child Tickets

Change History (5)

comment:1 Changed 19 months ago by nickm

Alternatively, we could do this with more branches in the tor.git repository. We would need to mark the semantic branches (alpha, stable, lts) as "okay to force-push".

comment:2 Changed 19 months ago by teor

I like the idea of a separate repository.

If we only list supported releases, we may have to mark release branches as "ok to delete", so we can delete releases when they become unsupported.

Edit: spelling, expand

Last edited 19 months ago by teor (previous) (diff)

comment:3 Changed 19 months ago by dgoulet

I'm still spotty on the rationale for this. Is it because we want to allow relay operator to be able to "git pull" and always get the latest stable?

Doing the devil advocate here: if this is the only use case, we are adding more work at maintaining Tor properly for something that I don't think its worth doing.

If it is, then fair enough for a second repository. And maybe that could be something nickm does *not* maintain if the overhead is just too much.

comment:4 Changed 19 months ago by nickm

Milestone: Tor: 0.3.3.x-finalTor: unspecified

Throwing this into unspecified until we have a better sense of why we'd want to do this.

comment:5 Changed 14 months ago by teor

Status: assignednew

Make everything that is assigned to no-one new again.

Note: See TracTickets for help on using tickets.