Opened 4 years ago

Closed 4 years ago

#17530 closed enhancement (invalid)

Update release process documentation for hardened Tor Browser

Reported by: gk Owned by: gk
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: TorBrowserTeam201511R, GeorgKoppen201511
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

We should add the steps needed for making a hardened Tor Browser release to the release process document.

Child Tickets

Attachments (1)

0001-Bug-17530-Update-release-process-for-hardened-builds.patch (902 bytes) - added by gk 4 years ago.

Download all attachments as: .zip

Change History (3)

comment:1 Changed 4 years ago by gk

Status: newneeds_review

Patched attached, please review and merge.

comment:2 Changed 4 years ago by gk

Keywords: TorBrowserTeam201511R added; TorBrowserTeam201511 removed
Resolution: invalid
Status: needs_reviewclosed

On a second thought, there should be no need for a special treatment of hardened releases here at all. If there are things that need to get merged into the hardened-builds branch then this should get done right after they got committed to master. All that remains then is the usual boilerplate stuff that is already codified in the release process documentation and is done after checking out the proper branch to build from.

Note: See TracTickets for help on using tickets.