Discussion on use of Release posts for bug notification
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Proposal
We need to identify what our SSOT for bugs, regressions and bug fixes are and ensure that that is easily findable and searchable.
Details
Our release posts are GitLab.com focussed in that it is only really useful when viewed in the perspective of the upcoming GitLab.com release. This puts our self-managed customers at a disadvantage because there is no easy way to determine which bugs or regressions appear at what point of their upgrade path.
Scenario
Imagine that you are a GitLab Ultimate customer with over a hundred users. After upgrading to GitLab v16.5, an Ultimate feature becomes unusable or unreliable. Please search through our release posts to identify whether this is a bug, a result of a failed upgrade or some deprecation causing the feature to be unreliable.
Example
This is what is happening with this bug in a GitLab Ultimate feature: Dismissed vulnerabilities in Pipeline security ... (#367298 - closed). It is making every Ultimate customer that updates to a specific range of GitLab versions question that ultimate feature's reliability and stability:
Creating a more searchable resource for bugs etc will help our customers be able to consider GitLab to be a more reliable and stable product instead of less.