Improve monthly RP bugs and performance triage
What does this MR do and why?
Describe in detail what your merge request does and why.
See Improve the Monthly Bug & Performance Issues Tr... (#1336 - closed)
The monthly release process no longer requires EMs to manually add bugs and performance issues to the release post. Instead, these will be automatically linked from issue lists if they have the correct status and labels.
The Bug and Performance Issue triage reports are no longer required in their current format and the guidance is out of date.
This MR:
- Merges both policies into one policy.
- Improves the guidance for what's required.
- Clearly splits sections into what will and won't be included in the RP post.
- Retains checkboxes so that EMs can collaborate within a stage without duplicating effort.
- Removes markdown boxes as there's no longer a requirement to copy and paste text into an MR.
Expected impact & dry-runs
Click to expand
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.
project_management
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 @donaldcook
:
product_planning
Frontend issues
Please review these issues, which are in a late workflow stage or are closed but will not be included in the release post @kushalpandya
:
product_planning
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 @kushalpandya
:
knowledge
Frontend issues
Please review these issues, which will be included in the release post @johnhope
:
-
Rich Text editor should enter normal new line w... (gitlab-org/gitlab#416119 - closed) - closed -
Autocomplete suggestions don't work when editin... (gitlab-org/gitlab#410081 - closed) - closed
knowledge
Frontend issues
Please review these issues, which are in a late workflow stage or are closed but will not be included in the release post @johnhope
:
-
Wiki titles on the sidebar overlap if they reac... (gitlab-org/gitlab#412894 - closed) - workflowin review
Ungrouped and Non-Specialized
Please review these issues, which will be included in the release post but are missing group and/or specialization labels @donaldcook @kushalpandya @johnhope @blabuschagne
:
Ungrouped
Please review these issues, which are missing group and/or specialization labels @donaldcook @kushalpandya @johnhope @blabuschagne
. These are in a late workflow stage or are closed but will not be included in the release post::
-
GitLab reference links are incorrect in content... (gitlab-org/gitlab#412316 - closed) - closed -
"Applying command" message stays visible for ne... (gitlab-org/gitlab#409364 - closed) - closed -
Permission Role for Guest is wrong in documenta... (gitlab-org/gitlab#403305 - closed) - closed
Closer 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.
/assign @donaldcook @kushalpandya @johnhope @blabuschagne
/due 16th
/label ~"devops::plan"
Action items
-
If adding environment variables for reactive processors, update config/triage-web.yaml
and.gitlab/ci/triage-web.yml
-
(If applicable) Add documentation to the handbook pages for Triage Operations => -
(If applicable) Identify the affected groups and how to communicate to them: -
/cc @ person_or_group
=> -
Relevant Slack channels => -
Engineering week-in-review
-