We now have a solid proposal.

We now have a solid proposal.

Release process: make it clear that one needs to login with default settings when generating an updated boot profile (Closes: #16466).

We want to optimize for the default settings.

The best we can do is remove them from our rsync server.

Following up on issues observed the first time someone did it
since my last updates.

Since #15583, if one merely follows what this test said, they would
*not* test /bin/su, nor input any of the potential default passwords
we want to check: instead they would see our "su" shell alias do its
job and tell that the administration password is disabled.

So let's make sure testers use /bin/su and actually test these passwords.

The previous command would yield "1.2G", which looks very similar to "1.2G" to
me, and could reflect any size increase < 100M, which does not achieve
what we're after here: a 50M size increase is already something we need
to investigate and possibly the symptom of a regression.

When one has a clone of our ISO history Git annex repository,
without this change the output has a very low signal/noise ratio.

For RCs (and alphas/betas) we ship /etc/os-release with
TAILS_CHANNEL="alpha" so the old instruction (simple append) would
result in two TAILS_CHANNEL entries. It happens to be the case that
Tails Upgrader will use only the first entry it encounters and ignore
any additional ones, so the old instructions will make us stay on the
"alpha" channel.