The current snapshots are actually at 2019080701 but I have seen FTBFS
on Jenkins (compile error for virtualbox-guest) and a different one
locally (Tor Browser AppArmor profile patch doesn't apply) so I'll
pick the most recent snapshots I successfully built to avoid having to
delay the release further.

In commit 31c44296 this patch was erroneously removed: the restored
patch was *not* upstreamed, so we still need to apply it.

Currently translated at 44.4% (4 of 9 strings)

Currently translated at 44.4% (4 of 9 strings)

I.e. synchronize with the ikiwiki configuration used by our production website.

In the past we recommended forking us on gitlab.com, which was the only mirror
of our main Git repository (aka. tails.git) with a user-friendly "Fork" feature.

Since then, we have another such mirror — Salsa — that we actively use and keep
track of: for example, merge requests can be submitted there and the Foundations
Team will review them. This increases the chances that other teams start to do
the same there as well, until we've decided which GitLab instance will become
the canonical location for our code in the future.

This contrasts with gitlab.com, where we have disabled MRs on purpose.

So, let's point new contributors to a mirror where they can use the common "fork
and send a MR" workflow :)

This number has been decreasing since we wrote the installation
assistant. It went from 39080 in January 2016 down to 8003 in July 2019.

Currently translated at 33.3% (3 of 9 strings)

Fix-committed: #16789

As gronte said, "we've automated ourselves away there" :)

Currently translated at 27.4% (17 of 62 strings)

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