Commit ecfceac5 authored by intrigeri's avatar intrigeri

Upgrader: use the alpha channel when the next version will be an alpha, beta, or RC.

The basic idea here is to make it easy for users of 3.0~betaN to upgrade to the
next beta or RC, without having to type any command-line, and without having to
create UDFs for these upgrade paths on the "stable" update channel (that would
feel wrong, wouldn't it?).

Bonus: once this is in place, more generally we'll be able to update our release
process doc+scripts to stop creating meaningless "stable" channel upgrades for
RCs, such as upgrade/v1/Tails/2.10~rc1/i386/stable/upgrades.yml, that we have
been needing so far since our RCs thought they were using the "stable"
update channel.

refs: #12206
parent 9f7ad7d6
......@@ -112,6 +112,9 @@ cat >> config/chroot_local-includes/etc/os-release <<EOF
TAILS_PRODUCT_NAME="Tails"
TAILS_VERSION_ID="$AMNESIA_VERSION"
EOF
if echo "$AMNESIA_VERSION" | grep -qs -E '~(alpha|beta|rc)[0-9]*$' ; then
echo 'TAILS_CHANNEL="alpha"' >> config/chroot_local-includes/etc/os-release
fi
# changelog
cp debian/changelog config/chroot_local-includes/usr/share/doc/amnesia/Changelog
......
Markdown is supported
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