Project

General

Profile

Feature #17010

Write release notes for 4.0

Added by sajolida 2 months ago. Updated 23 days ago.

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

0%

Feature Branch:
web/release-4.0
Type of work:
End-user documentation
Blueprint:
Starter:
Affected tool:


Related issues

Blocks Tails - Feature #16711: Core work 2019Q3 → 2019Q4: Technical writing Confirmed 01/08/2016

Associated revisions

Revision d67b09be (diff)
Added by intrigeri 23 days ago

4.0 release notes: fix Linux version (refs: #17010)

Revision 6defe322 (diff)
Added by intrigeri 23 days ago

4.0 release notes: remove stray, duplicate HTML anchor (refs: #17010)

Revision 86c1ca4d (diff)
Added by intrigeri 23 days ago

4.0 release notes: make typography consistent (refs: #17010)

Revision 06802e8a (diff)
Added by intrigeri 23 days ago

4.0 release notes: update tor version number (refs: #17010)

Revision ececaf9f (diff)
Added by intrigeri 23 days ago

4.0 release notes: avoid misplaced line breaks with nbsp (refs: #17010)

Revision b90b4149 (diff)
Added by intrigeri 23 days ago

Update PO files (refs: #17010)

History

#1 Updated by sajolida 2 months ago

  • Blocks Feature #16711: Core work 2019Q3 → 2019Q4: Technical writing added

#2 Updated by sajolida about 1 month ago

  • Status changed from Confirmed to In Progress

I wrote a draft straight in devel.

@intrigeri Feel free to have a look at some point :) Though, I updating it again on the day of the release.

#3 Updated by intrigeri about 1 month ago

I wrote a draft straight in devel.

FYI, one potential drawback (I did not test) is that it may show up as published in the doc included in 4.0~rc1.
Perhaps it's safer, in the future, not to add such announcements to branches that will, in the meantime, be used for another pre-release :)

intrigeri Feel free to have a look at some point :) Though, I updating it again on the day of the release.

Some thoughts of mine:

  • We fixed the swapgs vulnerability in Tails 3.16 and 4.0~beta2 already.
  • "The notification is bigger and more readable" ← even if I'm lucky enough to not need a screen reader and can see the screenshot, I don't know which notification you're referring to.
  • It's on purpose that you did not include all changes mentioned in the 4.0~beta1 release announcement, right?

#4 Updated by sajolida about 1 month ago

Perhaps it's safer, in the future, not to add such announcements to branches that will, in the meantime, be used for another pre-release :)

Oops! I clearly did not follow the documented process here and should
have wrote them in web/release-4.0 :(

  • We fixed the swapgs vulnerability in Tails 3.16 and 4.0~beta2 already.

I was not sure either because there are so many Spectre variants :)

Fixed in 08e0a6c3ea.

  • "The notification is bigger and more readable" ← even if I'm lucky enough to not need a screen reader and can see the screenshot, I don't know which notification you're referring to.

I meant the "notification area", but I checked and actually it's neither
bigger nor more readable. It just looks a bit different and it not worth
mentioning.

Removed in 893d87ec2e.

  • It's on purpose that you did not include all changes mentioned in the 4.0~beta1 release announcement, right?

Yes. But you made me realize that it's probably good to always mention
when we remove something. See 106839c99d. Do you think that there would
be anything else being worth mentioning?

Added in 106839c99d.

#5 Updated by intrigeri about 1 month ago

Hi,

I've looked at your changes and they look good to me!

However, you pushed them to the devel branch after the freeze for 4.0, which will be prepared based on the testing branch. So if we leave things as-is, these changes will only be applied to the 4.0 release notes when we release 4.2 or 4.3 (whichever the following major release is). That's a bit late :)

So, please fork a web/release-4.0 branch off testing and cherry-pick your new commits there.
Thanks in advance!

Similarly, any other doc work aimed at 4.0 should now be based on the testing branch.

#6 Updated by intrigeri 24 days ago

  • Priority changed from Normal to High
  • Feature Branch set to web/release-4.0

Hi,

intrigeri wrote:

So, please fork a web/release-4.0 branch off testing and cherry-pick your new commits there.

I did this myself. The changelog is available there so you can now update the release notes accordingly.
I'll let you judge if you want to document fixes for bugs that never existed in 3.x (e.g. all those that came with shipping Tor Browser 9.0aN in 4.0~rc1, this sort of things).

Bumping priority to ensure this is close to the top of your radar today :)

#7 Updated by intrigeri 23 days ago

I don't know if you'll show up in time for the release today, so I've updated the draft release notes a bit (see commits referencing this ticket) in order to give translators some time to do their work. The draft looks good enough to me now for publication so no big deal if you can't work on it again.

This being said, I can't find any Tweet. I can of course use the fallback text but given the importance of 4.0 + the timing vs. our donation campaign, I think a nicer tweet with more exciting text and pictures would add lots of value. Worst case, if I don't hear from you until the release, I'll tweet the fallback text and you can reply to that tweet later with more stuff.

#8 Updated by sajolida 23 days ago

  • Assignee changed from sajolida to intrigeri

Tweet:

Tails 4.0 is out: https://tails.boum.org/news/version_4.0/.

Our most important release in years:

- Adds @KeePassXC
- Fixes @ElectrumWallet
- Updates OnionShare @micahflee
- Updates to @Debian 10
- Includes tons of performance and usability improvements, especially for non-English speakers

Images:

  • languages.png
  • keepassxc.png
  • onionshare.png
  • screen-keyboard.png

I'm mentioning micahflee because he's quite big on Twitter (and a friend).

#9 Updated by intrigeri 23 days ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF