Opened 5 years ago

Closed 5 years ago

#17918 closed enhancement (fixed)

Update release process documentation to check for new Firefox tag immediately before releasing

Reported by: gk Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: MikePerry201512R, TorBrowserTeam201602R
Cc: mikeperry Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


To prevent things like #17877 from happening ever again we should mention to check the release is built from the proper Mozilla release tag immediately before we push the "Go live" button.

Child Tickets

Attachments (1)

0001-Bug-17918-Make-sure-we-use-correct-Firefox-tag.patch (836 bytes) - added by gk 5 years ago.

Download all attachments as: .zip

Change History (5)

comment:1 Changed 5 years ago by gk

Cc: mikeperry added
Keywords: TorBrowserTeam201512R MikePerry201512R added
Status: newneeds_review

The patch is attached for review and merge.

comment:2 Changed 5 years ago by gk

Keywords: TorBrowserTeam201601R added; TorBrowserTeam201512R removed

Carrying over reviews.

comment:3 Changed 5 years ago by gk

Keywords: TorBrowserTeam201602R added; TorBrowserTeam201601R removed

Carrying over review tickets.

comment:4 Changed 5 years ago by gk

Resolution: fixed
Status: needs_reviewclosed

This is just adding a comment, so I'll take it as is. commit 233ca723c71360793fcf86110e4af611e2f52361 on tor-browser-spec master has it.

Note: See TracTickets for help on using tickets.