Completed bug and performance issues for the RP
This triage issue helps ensure bug fixes and performance improvements are included in the monthly release post.
To be included, the issues must:
- Be closed.
- Include both the correct milestone and the workflowcomplete label.
For each issues below, you should:
- Determine if the issue has been completed.
- If yes:
- Add the workflowcomplete label.
- Confirm the milestone is correct.
- Make sure the issue is closed.
- Check off the task item to show it's been reviewed.
source_code
Frontend issues
Please review these issues, which will be included in the release post @andr3:
-
gitlab-org/gitlab#511688+ - closed
source_code
Backend issues
Please review these issues, which will be included in the release post @andrevr:
source_code
Backend issues
Please review these issues, which are in a late workflow stage or are closed but will not be included in the release post @andrevr:
import
Backend issues
Please review these issues, which are in a late workflow stage or are closed but will not be included in the release post @thiagocsf:
Ungrouped and Non-Specialized
Please review these issues, which are missing group and/or specialization labels @andr3 @andrevr @francoisrose @adebayo_a @thiagocsf. These are in a late workflow stage or are closed but will not be included in the release post:
-
Bug: Branch pushes intermittently fail to trigg... (gitlab-org/gitlab#572341) - workflowin review -
MR sticky header overscroll behavior is buggy (gitlab-org/gitlab#560204 - closed) - closed
workflowcomplete and missing issues
MissingCloser to the end of the milestone, you should:
-
Check the issue list for completed issues that don't have the workflowcomplete label. -
Review Merge Requests for any fixes without a corresponding issue, and create issues for them.