Skip to content

Improve monthly RP bugs and performance triage

John Hope requested to merge improve-rp-triage-issues into master

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:

  1. Merges both policies into one policy.
  2. Improves the guidance for what's required.
  3. Clearly splits sections into what will and won't be included in the RP post.
  4. Retains checkboxes so that EMs can collaborate within a stage without duplicating effort.
  5. 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:

  1. Be closed.
  2. Include both the correct milestone and the workflowcomplete label. For each issues below, you should:
  3. Determine if the issue has been completed.
  4. If yes:
    • Add the workflowcomplete label.
    • Confirm the milestone is correct.
    • Make sure the issue is closed.
  5. 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:

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:

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::

Closer to the end of the milestone, you should:

/assign @donaldcook @kushalpandya @johnhope @blabuschagne
/due 16th
/label ~"devops::plan"

Action items

Edited by John Hope

Merge request reports