Project

General

Profile

Bug #16690

Upgrade to Tor Browser based on Firefox 60.7

Added by intrigeri 5 months ago. Updated 4 months ago.

Status:
Duplicate
Priority:
Elevated
Assignee:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:
Browser

Related issues

Related to Tails - Bug #16706: NoScript gets disabled after a while Resolved
Duplicates Tails - Feature #16337: Upgrade to Tor Browser 8.5 Resolved 03/15/2019
Blocks Tails - Feature #16209: Core work: Foundations Team Confirmed

History

#1 Updated by intrigeri 5 months ago

#2 Updated by intrigeri 5 months ago

#3 Updated by intrigeri 4 months ago

#4 Updated by intrigeri 4 months ago

  • Related to Bug #16706: NoScript gets disabled after a while added

#5 Updated by CyrilBrulebois 4 months ago

The Tor Browser release seems to be delayed by one week.

@intrigeri: Do we postpone 3.14 accordingly, or do we skip the Tor Browser update?

#6 Updated by intrigeri 4 months ago

The Tor Browser release seems to be delayed by one week.

Confirmed by https://wiki.mozilla.org/Release_Management/Calendar

Do we postpone 3.14 accordingly, or do we skip the Tor Browser update?

Shipping the planned Firefox / Tor Browser security updates is the main driver for our release schedule ⇒ we follow and postpone.

(By default, I assume you'll update the RM bits accordingly, shout if you can't :)

#7 Updated by CyrilBrulebois 4 months ago

intrigeri wrote:

Shipping the planned Firefox / Tor Browser security updates is the main driver for our release schedule ⇒ we follow and postpone.

That's what I thought; thanks for confirming.

(By default, I assume you'll update the RM bits accordingly, shout if you can't :)

If that means updating the calendar and following up to mails sent at the beginning (hrm…) of the shift, that was my plan. If you have other bits in mind, please mention which.

#8 Updated by intrigeri 4 months ago

(By default, I assume you'll update the RM bits accordingly, shout if you can't :)

If that means updating the calendar and following up to mails sent at the beginning (hrm…) of the shift, that was my plan. If you have other bits in mind, please mention which.

Nothing in mind, except updating the date of the target version on Redmine :)

#9 Updated by CyrilBrulebois 4 months ago

OK, I think I've done what was needed: checked TR availability for new date, informed tails-dev@, updated website, and updated Redmine roadmap.

#10 Updated by intrigeri 4 months ago

#11 Updated by intrigeri 4 months ago

  • Status changed from Confirmed to Duplicate
  • Assignee deleted (CyrilBrulebois)

Given there will be no 8.0.10, this ticket is moot => let's focus on #16337.

Also available in: Atom PDF