It's better to have sudo ask for a password upfront than letting the
wrapper start children which might lead to entangled sudo prompt and
log lines.

Wrong indentation was making the closing ')' hang below the code block.

Needed after the last few successive merges. :)

This can be useful:

 - To see items that are on our roadmap for this year, with no more
   specific milestone set

 - On release day, when "Milestone = Upcoming" does not display
   issues for the release being prepared

Ideally this page could be split in several more specific pages.

Conflicts:
	bin/copy-iuks-to-rsync-server-and-verify
	wiki/src/contribute/release_process.mdwn

A recent example is the switch to GitLab: one might have forgotten to
update the “Build” step in the parallel_build_IUKs job to point at the
new remote.

v2: Use names agreed on in #17658

Conflicts:
	wiki/src/contribute/release_process.mdwn

Closes #17527

GitLab closes these issues automatically only when the destination
branch is the default branch, i.e. `master` currently:
https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically

I'm wondering if we should make the `stable` or `devel` branch our default
branch (assuming we merge more branches into these branches than into `master`),
but for now let's workaround the problem via documentation.

Bump our signing key's expiration date

Closes #17133

See merge request !17

Fix first list (and test gitlab)

See merge request !18

refs: #17133, tails/sysadmin#17391