Feature #13571

Write release notes for 3.2

Added by sajolida 2017-08-03 16:05:34 . Updated 2017-09-28 18:50:02 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_3.2
Start date:
2017-08-03
Due date:
% Done:

100%

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

Starter:
Affected tool:
Deliverable for:

Description

Subtasks

Related issues

Blocks Tails - Feature #13423: Core work 2017Q3: Technical writing Resolved 2017-07-05

History

#1 Updated by sajolida 2017-09-18 08:05:20

  • Assignee changed from sajolida to anonym
  • QA Check set to Ready for QA
  • Feature Branch set to web/13571-release-notes

Ready in web/13571-release-notes.

Note that screenshots/tails_installer_in_tails.png will be updated in doc/13301-no-splash-in-tails with the same file name.

Assigning to anonym. I think it’s better to have this reviewed by the RM for completeness and correctness than by other technical writers.

#2 Updated by anonym 2017-09-21 14:55:19

  • Assignee changed from anonym to sajolida
  • QA Check changed from Ready for QA to Info Needed

It seems (Bug #12740#note-23) Tails is now reproducible. Or at least there’s a good chance for it! So I think we should prepare a short paragraph about this and its importance. Or is this too geeky? What is your take on this?

#3 Updated by sajolida 2017-09-22 11:55:47

  • Assignee changed from sajolida to anonym
  • QA Check changed from Info Needed to Ready for QA

Yes, once the reproducibiliy can be announce it could be mentioned in the release notes. Now, this explanation in the release notes should be short and I think it would work best if it goes along a more in depth blog post about it on our blog, once we’re ready for that. For example, that what I thought Feature #14520 was about but I only see it posted on intrigeri’s blog on people.debian.org.

So I’ll wait until it’s been communicated to our community before mentioning it from the release notes.

By the way, I updated the draft notes with the removal of XTEST.

#4 Updated by intrigeri 2017-09-22 12:04:23

> By the way, I updated the draft notes with the removal of XTEST.

I guess you mean the “revert of the removal of XTEST” :)

#5 Updated by sajolida 2017-09-25 11:43:38

  • Status changed from Confirmed to In Progress

Applied in changeset commit:4f3a46a99d1194af5a9f179faaeaa5935586e164.

#6 Updated by anonym 2017-09-25 16:46:45

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 0 to 100
  • QA Check changed from Ready for QA to Pass

#7 Updated by anonym 2017-09-28 18:50:02

  • Status changed from Fix committed to Resolved

#8 Updated by sajolida 2017-10-02 18:24:49