Normally, the list of CVEs has been reported on our issue already.

Yesterday the TR wrote "but I need to know the TR", while this info
was available a bit further on the pad. Let's point them to it
earlier, and while I'm at it, offer a way forward when the info
is actually missing.

The previous version, once pasted into a pad, generates this broken link:

  https://tails.boum.org/contribute/calendar/)/

Currently translated at 35.3% (6 of 17 strings)

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

Currently translated at 73.0% (100 of 137 strings)

Currently translated at 73.0% (100 of 137 strings)

Currently translated at 17.4% (4 of 23 strings)

Currently translated at 17.4% (4 of 23 strings)

There's only 1 file to delete there.

Don't use undefined "one" subject.

Say "must" and not "should" when it's not optional.

Don't use passive voice.

When the RM lands here, it's easy to despair, especially if their Internet
connection is poor. For example, today I was not thrilled at the idea of
uploading 11 GB of data to an Onion service. But actually it's very fast in the
case at hand, so let's tell the RM there's still hope.

Currently translated at 71.5% (98 of 137 strings)

The build_IUKs job is obsolete and unmaintained.

This should mitigate the "have to wait for up to 15 minutes" issue here,
which some RMs have suffered from in the past.

Here we care only about the latest directory entry.

Fixes regression introduced in c29cb641
(#17686).

One can't do "Build the Incremental Upgrade Kits on Jenkins" without first
having done "ISO history".

We don't need root to measure time. At least on my system, "sudo time" fails
with "command not found". But "time sudo" works just fine.

Fixes regression introduced in bfb863f5.

We have a good, working solution. Let's just use it, and skip the lengthy
explanation about why it's good, and what other, worse options one may
choose instead.

Explaining the pros and cons of the new setup may have helped
at some point. I think we're way past this time now.

One needs this info to compute hashes of the locally-built images.