GitLab

GitLab publishes known issues as a structured section of each monthly release post, one of the more disciplined practices in open-source project maintenance. The section is mandated by the release post template, which means it appears across releases as a matter of process rather than editorial discretion. That structural commitment is the notable thing: the known-issues surface exists reliably, not only when something went visibly wrong.

The handbook’s engineering releases page describes the process; the operational surface is the release posts themselves at about.gitlab.com/releases. Each post carries upgrade notes, deprecation notices, and the known-issues block as a consistent trio. For teams running self-managed GitLab, the upgrade notes subsection is typically the higher-stakes read, since GitLab’s upgrade path has historically carried hard constraints around skipping minor versions.