GitLab

Since 4.2 (January 7), people can upgrade directly to the latest
version.

/upgrade/tails is visited 4 times more than /upgrade/clone, despite
being more complicated and longer.

Putting it first also increases the visibility of the links with the
different operating systems, which is what most people will need on this
page.

- Everybody doing a manual upgrade will go through the download page
  while they might not all go through /doc/upgrade.
- Reading the release notes while downloading sounds less trouble.
- People doing automatic upgrades are already pointed to the release
  notes.

If we want more people to read the release notes, the real solution will
be in #17068.

It's not really useful here. We already document how to check the
version of Tails in more useful places, like all cloning scenarios.

We propose manual upgrades from a regular OS because it might be:

  - Faster to do download (eg. Torrent)
  - Less intrusive
  - Possible to do proactively

Even though it might be a bit less safe.

- We've had 2 places to document manual upgrades since 2016,
  /doc/upgrade then pointing to /upgrade for the actual meat. Having a
  single place prevents people to jump around needlessly.

- Tails Upgrader has been pointing to /doc/upgrade since 2014 and these
  old versions of Tails will continue to point to it.

- We could as well redirect /doc/upgrade/#manual to /upgrade but
  /doc/upgrade has the advantage of putting both techniques in
  perspective.

- /doc/upgrade (formerly /doc/first_steps/upgrade) is very well indexed
  by search engines while we prevented /upgrade to be indexed by
  'noindex'.

We already scream about this on every boot, if people land on this page,
they know this already.

They probably makes more sense there and will be more visible because
the section is less crowded.

Currently translated at 17.7% (11 of 62 strings)

Translation: Tails/wiki/src/news/version_3.14.1.*.po
Translate-URL: http://translate.tails.boum.org/projects/tails/wikisrcnewsversion_3141po/pt/

Currently translated at 39.0% (16 of 41 strings)

Translation: Tails/wiki/src/news/version_3.11.*.po
Translate-URL: http://translate.tails.boum.org/projects/tails/wikisrcnewsversion_311po/it/

Now we can assume that all Tails USB sticks were installed in the same
way.

Now that we are distributing USB images, USB sticks installed using
Etcher or GNOME Disks are the same as USB sticks installed using Tails
Installer

As per sajolida's request on
https://redmine.tails.boum.org/code/issues/14754#note-38

That we have breadcrumbs instead of 'Back' buttons, the previous layout
($scenario/overview) created a parent link to the steps for this
scenario:

	install » linux » usb » Install from Linux: overview

This commit makes them:

	install » linux » Install from Linux: overview

This will be especially useful for the upcoming download pages...

We now have a screenshot with a dialog box proposing a manual upgrade

Remove obsolete image

We used this terminology as a shortcut when we were supporting both USB
sticks and SD cards but now it's almost always superfluous, so let's
talk explicitly about USB stick as much as possible.

Website: explicitly add sort="age" to all inline directives I can easily & mechanically patch (refs: #12053).

A serious performance regression was brought by ikiwiki 3.20150614. One of the
few changes introduced in that release was to change the default sorting, for
inline directives, from "age" to "age title". Presumably the latter is
substantially slower, possibly since it has to process the *content* of all
included pages in order to retrieve their title, which may mean that a subset of
pages are processed more than once.

Conflicts:
	wiki/src/doc/first_steps/upgrade.mdwn