policy/tpa-rfc-80-debian-trixie-upgrade-schedule.md

@@ -33,7 +33,7 @@ The [freeze dates announced by the debian.org release team][] are:
 
 We have entered the "transition and toolchain freeze" which locks
 changes on packages like compilers and interpreters unless
-exceptions. See the [Debian freeze policy](https://release.debian.org/testing/freeze_policy.html) for an explanation of
+exceptions. See the [Debian freeze policy][] for an explanation of
 each step.
 
 Even though we've just completed the Debian 11 ("bullseye") and 12
@@ -44,9 +44,10 @@ having a year or two (2026-2027?) *without* any major upgrades.
 This proposal is part of the [Debian 13 trixie upgrade milestone][],
 itself part of the [2025 TPA roadmap][].
 
-[Debian 13 trixie upgrade milestone]: https://gitlab.torproject.org/groups/tpo/tpa/-/milestones/12
-[2025 TPA roadmap]: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/roadmap/2025
-[freeze dates announced by the debian.org release team]: https://lists.debian.org/debian-devel-announce/2025/01/msg00004.html
+ [freeze dates announced by the debian.org release team]: https://lists.debian.org/debian-devel-announce/2025/01/msg00004.html
+ [Debian freeze policy]: https://release.debian.org/testing/freeze_policy.html
+ [Debian 13 trixie upgrade milestone]: https://gitlab.torproject.org/groups/tpo/tpa/-/milestones/12
+ [2025 TPA roadmap]: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/roadmap/2025
 
 # Proposal
 
@@ -146,7 +147,7 @@ Concretely, we're planning on changing the `latest` container image
 tag to point to `trixie` in early April. A full *year* later, the
 `bookworm` container images will be retired. Note that we are already
 planning the retirement of the "old stable" (`bullseye`) container
-images, see [tpo/tpa/base-images#19](https://gitlab.torproject.org/tpo/tpa/base-images/-/issues/19), for which you may have
+images, see [tpo/tpa/base-images#19][], for which you may have
 already been contacted.
 
 New `idle` canary servers will be setup in Debian 13 to test
@@ -159,6 +160,7 @@ procedure in the past, in particular, but the whole procedure is now
 considered ripe for automation, see [tpo/tpa/team#41485][] for
 details.
 
+ [tpo/tpa/base-images#19]: https://gitlab.torproject.org/tpo/tpa/base-images/-/issues/19
  [tpo/tpa/team#41485]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/41485
 
 ### Batch 1: low complexity
@@ -230,11 +232,10 @@ batch took longer.
 It's probably safe to estimate 20 hours (30 minutes per machine) for
 this work, in a single week.
 
-[first batch of bookworm machines]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/41251
-
 Feedback and coordination of this batch happens in [issue batch 1][].
 
-[issue batch 1]:  "https://gitlab.torproject.org/tpo/tpa/team/-/issues/42071"
+ [first batch of bookworm machines]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/41251
+ [issue batch 1]:  "https://gitlab.torproject.org/tpo/tpa/team/-/issues/42071"
 
 ### Batch 2: moderate complexity
 
@@ -315,11 +316,10 @@ The [second batch of bookworm upgrades][] took 33 hours for 31
 machines, so about one hour per box. Here we have 57 machines, so it
 will likely take us 60 hours (or two weeks) to complete the upgrade.
 
-[second batch of bookworm upgrades]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/41252
-
 Feedback and coordination of this batch happens in [issue batch 2][].
 
-[issue batch 2]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/42070
+ [second batch of bookworm upgrades]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/41252
+ [issue batch 2]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/42070
 
 ### Batch 3: high complexity
 
@@ -372,14 +372,13 @@ possibly 20h.
 - [ ] translate.lizard
 ```
 
-[bookworm Ganeti upgrade]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/41254
-
 The challenge with Tails upgrades is the coordination with the Tails
 team, in particular for the Jenkins upgrades.
 
 Feedback and coordination of this batch happens in [issue batch 3][].
 
-[issue batch 3]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/42069
+ [bookworm Ganeti upgrade]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/41254
+ [issue batch 3]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/42069
 
 ### Cleanup work
 
@@ -431,7 +430,7 @@ We are clear, however, that we will not postpone an upgrade for a
 server retirement. Dangerzone, for example, is scheduled for
 retirement ([TPA-RFC-78][]) but is still planned as normal above.
 
-[TPA-RFC-78]: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-78-dangerzone-retirement
+ [TPA-RFC-78]: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-78-dangerzone-retirement
 
 # Costs
 
@@ -484,11 +483,10 @@ being affected by the upgrade.
 Comments or feedback can be provided in issues linked above, or the
 general process can be commented on in issue [tpo/tpa/team#41990][].
 
-[tpo/tpa/team#41990]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/41990
-
 # References
 
  * [Debian 13 trixie upgrade milestone][]
  * [discussion ticket][tpo/tpa/team#41990]
 
-[TPA bookworm upgrade procedure]: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/upgrades/bookworm
+ [TPA bookworm upgrade procedure]: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/upgrades/bookworm
+ [tpo/tpa/team#41990]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/41990