💡 Should the "GitLab XX changes" page be structured (like 'Deprecations and removals by version')?

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Label this issue
• Close this issue

Each item in the Deprecations and removals by version list has a YAML file like this one with the specific information about that item.

The "GitLab XX changes" pages have no such structure: should they?

👍 / 😐 / 👎 Considerations

• 👍 We could, for example, have a component key. Folks could then filter the list of items on that page by component instead or having to scroll through the page of Find in page.
• 👍 Having a template for adding items to this page helps to make sure relevant details are consistently considered and included.
• 😐 Any structure would have to flexible enough to comfortably support the kinds of content that appears on that pae.
• 👎 There's a chance that the structure that the template introduces makes it a bit more difficult for some folks to add items to this page. I suspect this will be limited: the structure will make it easier for folks to understand how to add a particular problem to this page.

✨ Why

The "GitLab XX changes" pages (like GitLab 17 changes) are a very important part of how the GitLab Support team and customers work to rapidly identify whether a particular upgrade-related problem is a known issue. As a part of WorkingGroupUpgradeImprovements @.luke and I discussed possible improvements and wanted to open a broader conversation about whether (and when) this idea is worth pursuing.