Opened 8 years ago

Closed 5 years ago

#4401 closed defect (fixed)

Find a way to stick meaningful version numbers on binaries built straight from maint

Reported by: katmagic Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Keywords: tor-client
Cc: git Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I once reverted to a remotely exploitable version of Tor when git describe master told me it was the one master was based on. This is confusing. Releases should have -p* tags.

Child Tickets

Change History (6)

comment:1 Changed 8 years ago by nickm

The problem here is that bumping the versions in maint, the way that we would currently try to do that, has repurcussions in the downstream branches. So maybe this should be: "Find a way to stick meaningful version numbers on binaries built straight from maint"

comment:2 Changed 8 years ago by nickm

Milestone: Tor: unspecified

comment:3 Changed 7 years ago by nickm

Priority: minornormal
Summary: The Tor release checklist should say to bump the version number on maint-* after every security bugfix.Find a way to stick meaningful version numbers on binaries built straight from maint

comment:4 Changed 7 years ago by nickm

Keywords: tor-client added

comment:5 Changed 7 years ago by nickm

Component: Tor ClientTor

comment:6 Changed 5 years ago by nickm

Resolution: fixed
Status: newclosed

Our current doc/HACKING instructions explain how to do this.

Note: See TracTickets for help on using tickets.