Commit 719a90da authored by intrigeri's avatar intrigeri
Browse files

Release process: remove obsolete note (refs: #15287)

This problem has not happened since a few years, mostly because I'm now aware of
it and thus careful. Moreover, we now have a build_IUKs Jenkins job, that takes
a TAILS_GIT_COMMIT parameter, and can thus be used to test new IUK generation
code before it's merged and affects a RM, on real-world scenarios. I'm using
this regularly when working on the IUK codebase. As it happens, this job runs on
Jenkins' isobuilders, that currently run Stretch.

So all things considered, I'm now confident that this note does more
harm (scaring the RM) than good (providing useful and actionable information).
parent ef9e64a1
......@@ -831,11 +831,6 @@ Build the Incremental Upgrade Kits
--outfile \"${ISOS:?}/Tails_amd64_${source_version:?}_to_${VERSION:?}.iuk\""
Note that developer tools for creating IUK and upgrade-description
files are primarily developed and tested on Debian sid. They may
therefore occasionally be broken on Debian stable. As of December 2019
they work fine on Debian Stretch.
<a id="reproducibility-sanity-check-iuk"></a>
Note that we do not yet build IUKs on Jenkins, otherwise here would be
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment