Bug #16405

release_process: fix mind-boggling instructions for --previous options

Added by CyrilBrulebois 22 days ago. Updated about 3 hours ago.

In Progress
Target version:
Start date:
Due date:
% Done:


QA Check:
Dev Needed
Feature Branch:
Type of work:
Contributors documentation
Affected tool:


Spotted during the 3.10, 3.11, and 3.12 release processes…

The instructions regarding the --previous options to pass to ./bin/tails-iuk-generate-upgrade-description-files are rather confusing and almost entirely the opposite of current practice; the latter would rather be: pass --previous $iuk for each iuk in ${IUK_SOURCE_VERSIONS?:}

Associated revisions

Revision 625ceaf0 (diff)
Added by anonym 7 days ago

Release process: automate "mind-boggling" manual step (Will-fix: #16405).

Regarding this removed part:

Older versions for which there is no incremental upgrade path to
the new release must be passed with `--previous-version` [...]

We haven't been doing this at all for a long time because of what's
said later:

Note that multi-steps incremental upgrade paths are valid and
supported [...]

We've instead been pushing these multi-step upgrades hard, so we've
basically never followed these instructions, so let's just kill them
for the benefit for future, stressed out RMs.


#1 Updated by anonym 7 days ago

  • Status changed from Confirmed to In Progress

#2 Updated by anonym 7 days ago

  • Assignee changed from anonym to intrigeri
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA
  • Feature Branch set to doc/16405-previous-iuks

@intrigeri, could you just double-check that I didn't mess this one up?

#3 Updated by intrigeri 1 day ago

intrigeri, could you just double-check that I didn't mess this one up?

Thanks! I'm on it. I'll come up with a proposal that fixes the obvious UX problem we have here, without removing useful info.

#4 Updated by intrigeri about 3 hours ago

  • Target version set to Tails_3.13
  • QA Check changed from Ready for QA to Dev Needed

Also available in: Atom PDF