Today if we want to call out a known issue in a released version we just add a new ad-hoc item to the release notes of all affected versions. This is kind of a pain, and it's easy to miss versions or for the notes to end up inconsistent across branches/backports etc. See for instance the docs fixes in #111014.
Could we instead introduce a more formal entity to represent each known issue, perhaps something like the file-per-PR changelog structure, to make it harder to make mistakes or miss copying the known issue docs to all the right places?
Today if we want to call out a known issue in a released version we just add a new ad-hoc item to the release notes of all affected versions. This is kind of a pain, and it's easy to miss versions or for the notes to end up inconsistent across branches/backports etc. See for instance the docs fixes in #111014.
Could we instead introduce a more formal entity to represent each known issue, perhaps something like the file-per-PR changelog structure, to make it harder to make mistakes or miss copying the known issue docs to all the right places?