Bug #16690
Upgrade to Tor Browser based on Firefox 60.7
0%
Description
Subtasks
Related issues
Related to Tails - |
Resolved | ||
Is duplicate of Tails - |
Resolved | 2019-03-15 | |
Blocks Tails - Feature #16209: Core work: Foundations Team | Confirmed |
History
#1 Updated by intrigeri 2019-05-03 16:53:37
- blocks Feature #16209: Core work: Foundations Team added
#2 Updated by intrigeri 2019-05-03 16:55:47
- blocked by
Feature #16337: Upgrade to Tor Browser 8.5 added
#3 Updated by intrigeri 2019-05-06 18:09:49
- blocks deleted (
)Feature #16337: Upgrade to Tor Browser 8.5
#4 Updated by intrigeri 2019-05-06 18:11:19
- related to
Bug #16706: NoScript gets disabled after a while added
#5 Updated by CyrilBrulebois 2019-05-09 10:45:48
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 2019-05-09 11:03:23
> 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 2019-05-09 11:29:56
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 2019-05-09 17:39:30
>> (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 2019-05-10 14:51:28
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 2019-05-17 14:44:34
- is duplicate of
Feature #16337: Upgrade to Tor Browser 8.5 added
#11 Updated by intrigeri 2019-05-17 14:45:03
- 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 Feature #16337.