Hi,
When generating the upgrade-description files for 0.23 I issued the
following command:
VERSION=0.23
PREVIOUS_VERSION=0.22.1
NEXT_VERSION=1.0
MAJOR_RELEASE=1
( cd $IUK_CHECKOUT && \
./bin/tails-iuk-generate-upgrade-description-files \
--version "$VERSION" \
--next-version "$NEXT_VERSION" \
--next-version "${NEXT_VERSION}~rc1" \
--iso "$ISOS/tails-i386-$VERSION/tails-i386-$VERSION.iso" \
--previous-version "$PREVIOUS_VERSION" \
--previous-version "${VERSION}~rc1" \
--previous-version 0.22 \
--iuks "$ISOS" \
--release-checkout "$RELEASE_CHECKOUT" \
--major-release "$MAJOR_RELEASE" \
)
This was copy-pasted from the example in the release process docs, and I
only added `--previous-version 0.22`. However, I suppose I should've
also one it for 0.22~rc1 and (the incorrectly named?) 0.22-rc2?
The results of the above command were committed in 7daac40, and as you
can see it removes the incremental upgrade path from 0.22 to 0.22.1,
replacing it with only the full upgrade to 0.23. The people that tested
the incremental upgrade paths for the 0.23 release wondered if removing
the 0.22 -> 0.22.1 -> 0.23 incremental upgrade path is intentional. It
will be available for those that have done the 0.22.1 incremental
upgrade before 0.23 goes live, but not to those that do it afterwards,
which they found weird.
Some clarification (and, possibly, discussion) for when to EOL
incremental upgrade paths seems in place. In particular, and somewhat
more urgently, what is the correct thing for the imminent 0.23 release?
Also, what about the alpha channel? We currently still have e.g. the
0.22.1_to_0.23~rc1 incremental upgrade path; the current process doesn't
clean them up.
Related to this is what to do with "orphaned" IUKs that no longer is
part of any described upgrade path. I suppose a step for cleaning up
orphaned IUKs from the rsync server should be added to after "Go wild!"
-> "Push".
Cheers!
