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/

We happen to thaw snapshots at different stages than after releasing.

This is not hypothetical, it's how we've been doing it for a while now.

APT time-based snapshot: document more thoroughly how to stop tracking a Debian distribution (refs: #11912).

It was apparently split but the "&& \" was not removed.

We need to use a different subshell each time we cd into a different
directory using a relative path, otherwise only the first cd works.

Let's always encode, on the stable branch, the exact set of APT snapshots we
want to use in next point-release. Previously we would pretend to thaw them by
writing "latest" in APT_snapshots.d/*/serial, but then apt-mirror would
special-case this situation: on an unreleased branch based on stable, it would
consider that "latest" means "stick to previous release's tagged snapshot".
Which worked fine at build time, except the part of our build system that
creates the build manifest does not know about this convention, so the resulting
build manifest would point to the latest APT snapshots we have, even though they
were not really used during the build. And even if the build manifest pointed to
the right place (i.e. the previous release's tagged APT snapshot), which is the
only place where some of the needed packages are when tagging the next
point-release's APT snapshot: tails-prepare-tagged-apt-snapshot-import does not
know how to generate a configuration that pulls from there.

So let's drop this special meaning of "latest", and make things simpler by
actually hard-coding in Git the snapshots we really want to use.

This implies the documentation change that makes sure that we're keeping these
time-based APT snapshots long enough.

refs: #11612

refs: #11448

refs: #11446

... and add placeholders wherever we need to document more hands-on
steps.

Non-RM:s might need it too.