Feature #16699

Write release notes for 3.13.2

Added by sajolida 2019-05-05 20:40:28 . Updated 2019-05-08 10:28:03 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
web/release-3.13.2
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Subtasks

History

#1 Updated by sajolida 2019-05-05 20:45:50

  • Feature Branch set to web/release-3.13.2

Here’s a draft in case I don’t show up in time tomorrow.

#2 Updated by anonym 2019-05-06 09:57:47

We need a known issue looking something like this: “Tor Browser is only safe (haha! sorry for being a troll :)) during the first run — if you want to restart Tor Browser, you need to restart Tails.”

#3 Updated by sajolida 2019-05-06 14:14:06

  • Assignee changed from sajolida to anonym
  • QA Check set to Ready for QA

Ready!

The tweet:

Tails 3.13.2 is out to reactivate NoScript and all our JavaScript protections after the add-ons incident in Firefox: https://tails.boum.org/news/version_3.13.2/.

#4 Updated by anonym 2019-05-06 15:03:21

  • Target version changed from Tails_3.13.2 to Tails_3.14

#5 Updated by intrigeri 2019-05-06 18:16:57

  • Status changed from Confirmed to Resolved
  • Assignee deleted (anonym)
  • Target version deleted (Tails_3.14)
  • QA Check changed from Ready for QA to Pass

This was merged.

#6 Updated by anonym 2019-05-06 19:46:29

@sajolida, in hindsight I have a few concerns with the release notes:

IMHO the visibility is too low for the known issue that NoScript will disappear after a while in case Tor Browser is restarted. Should we perhaps consider expanding that caution bubble a bit? Maybe add something like “In other words, avoid restarting Tor Browser, instead restart Tails.” I also think we should mention it in the “Known issues” section in order to be consistent (and reward users with the habit of reading them! :)).

Also, what about de-bloating the releases notes by just linking to the steps to re-enable NoScript in the security notice (since you copied them there)?

Lastly, the workaround to re-enable NoScript (flipping the pref) has consequences we don’t mention: now rogue add-ons (e.g. compromised versions of popular add-ons) can be installed manually, which is otherwise not possible. It might be nice to warn users that after using the workaround they really should refrain from installing any add-ons.

OTOH, 3.14 is here in a week, maybe I’m just wasting time here?

#7 Updated by sajolida 2019-05-08 10:28:03

> Maybe add something like “In other words, avoid restarting Tor Browser, instead restart Tails.”

Good idea! Done in 9741e854ae.

> I also think we should mention it in the “Known issues” section in order to be consistent (and reward users with the habit of reading them! :)).

Good idea as well. Done in b176f6680c.

> Also, what about de-bloating the releases notes by just linking to the steps to re-enable NoScript in the security notice (since you copied them there)?

On the web people don’t read, they scan. Taking up space (instead of
having a link) and having images here will increase the amount of people
noticing that there are some worthwhile instructions in there.

> Lastly, the workaround to re-enable NoScript (flipping the pref) has consequences we don’t mention: now rogue add-ons (e.g. compromised versions of popular add-ons) can be installed manually, which is otherwise not possible. It might be nice to warn users that after using the workaround they really should refrain from installing any add-ons.

I already spent more than my monthly technical writing budget on these
release notes so I’ll skip this one :)