Bug #16598

release_process: please clarify UDF checks

Added by CyrilBrulebois 2019-03-21 00:58:21 . Updated 2019-03-22 20:22:06 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2019-03-21
Due date:
% Done:

100%

Feature Branch:
Type of work:
Contributors documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Current post-release step:

1. Make sure there are upgrade-description files for any new versions
   that were added in the `debian/changelog` file since the last
   release. Background: From time to time the UDF generation/update
   step isn't perfect and entries might be missing from
   `wiki/src/upgrade/v1/Tails/<VERSION>/<ARCH>/<CHANNEL>`.

I have no idea what kind of check I’m supposed to do here.

Also, when releasing a new version: by definition, there are no new versions between the last release and this one? And the last release was passed as --previous to generate a UDF anyway?

→ I didn’t understand this step, at all.

Subtasks

History

#1 Updated by CyrilBrulebois 2019-03-21 01:44:51

Also, one is not supposed to touch the signing key after a given step has been reached (as we’ve seen during the 3.13 release cycle?). So I’m not sure fixing any missing UDF files would be reasonable as one of the last steps?

#2 Updated by intrigeri 2019-03-22 19:29:56

> Also, one is not supposed to touch the signing key after a given step has been reached (as we’ve seen during the 3.13 release cycle?). So I’m not sure fixing any missing UDF files would be reasonable as one of the last steps?

Exactly. Better let another RM fix up stuff later on, after the test suite alerted us about the problem.

#3 Updated by intrigeri 2019-03-22 20:22:06

  • Status changed from Confirmed to Resolved
  • % Done changed from 0 to 100

Applied in changeset commit:tails|fb6364743535b981f96cdc10ee144e39b7f3be2b.