Project

General

Profile

Bug #10885

Better integrate new upgrade scenarios with upgrade documentation

Added by sajolida over 3 years ago. Updated 28 days ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Installation
Target version:
Start date:
01/08/2016
Due date:
% Done:

0%

Feature Branch:
Type of work:
End-user documentation
Blueprint:
Starter:
Affected tool:
Installation Assistant

Description

For the release of the installation assistant, I did a quick fix but we could:

  • Deduplicate doc/first_steps/upgrade/release_notes.inline.
  • Merge /doc/first_steps/upgrade and /upgrade to prevent clicks and possible confusion.
  • Rethink where Tails Upgrader should point to.
  • Maybe mention release notes in IA.

Also, now that we are distributing USB images we should adapt /upgrade:

  • It could be done equally from Windows and macOS than "from Linux" (as currently advertized)

Related issues

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

History

#1 Updated by u over 1 year ago

Is this still up-to-date wrt the IA version2?

#2 Updated by sajolida over 1 year ago

We only redesigned the download page but haven't changed much the rest of the installation instructions :)

#3 Updated by sajolida about 2 months ago

  • Assignee deleted (sajolida)

#4 Updated by sajolida about 2 months ago

  • Assignee set to sajolida
  • Target version set to Tails_3.16
  • Parent task set to #16711

#5 Updated by sajolida about 1 month ago

  • Parent task deleted (#16711)

#6 Updated by sajolida about 1 month ago

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

#7 Updated by sajolida 28 days ago

  • Description updated (diff)
  • Target version changed from Tails_3.16 to Tails_4.0

The next people we'll rely on this heavily is for the release of 4.0.

Also available in: Atom PDF