2019-12-09 - Triage report for "group::progressive delivery"
Hi, @ogolowinski @darbyfrey @jhampton
This is a group or stage level triage package that aims to summarize the feature proposals and bugs which have not been scheduled or triaged. For more information please refer to the handbook:
Scheduling the workload is a collaborative effort by the Product Managers and Engineering Managers for that group. Please work together to provide a best estimate on priority and milestone assignments. For each issue please:
- Determine if the issue should be closed if it is no longer relevant or a duplicate.
- If it is still relevant please assign either a best estimate versioned milestone, the %Backlog or the %Awaiting further demand milestone.
- Specifically for ~bug, if there is no priority or clarity on a versioned milestone, please add a Priority label. Priority labels have an estimate SLO attached to them and help team members and the wider community understand roughly when it will be considered to be scheduled.
- Once a milestone has been assigned please check off the box for that issue.
- Please work with your team to complete the list by the due date set.
Feature Proposal Section
For the following feature proposals. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone.
Unscheduled feature with customer
-
#37482 (closed) CI Variables for Merge Trains Category:Continuous Delivery, ~"Merge Trains", ~"ci variables", customer, ~"devops::release", ~"devops::release::merge trains", feature, ~"group::progressive delivery"
Unscheduled feature (non-customer)
-
#37470 (closed) Ansible Template fot CI/CD gitlab.ci.yml file Category:Continuous Delivery, ~"devops::release", feature, ~"group::progressive delivery" -
#37346 (closed) Download Artefact on the MR widget Category:Continuous Delivery, UX, ~"devops::release", feature, ~"group::progressive delivery" -
#37260 (closed) Comment directly from the review app Category:Review Apps, UX, ~"devops::release", feature, ~"group::progressive delivery"
Bug Section
For the following bugs. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone and ensure that a priority label is set.
Heatmap for all bugs
Bugs for their priority and severity label are counted here. Every bug should have severity and priority labels applied. Please take a look at the bugs which fall into the columns indicating that the priority or severity labels are currently missing.
| ~S1 | ~S2 | ~S3 | ~S4 | ~"No severity" | |
|---|---|---|---|---|---|
| ~P1 | 0 | 0 | 0 | 0 | 0 |
| ~P2 | 0 | 4 | 1 | 0 | 0 |
| ~P3 | 0 | 0 | 18 | 0 | 0 |
| ~P4 | 0 | 0 | 0 | 8 | 0 |
| ~"No priority" | 1 | 0 | 1 | 0 | 2 |
Unscheduled ~bug (non-customer)
-
#37947 (closed) When a pipeline fails, manual build & deploy jobs are cancelled even if not triggered by anyone ~"S3", ~"bug", ~"devops::release", ~"group::progressive delivery" -
#36824 (closed) Transient failure in qa/specs/features/ee/browser_ui/6_release/pipelines_for_merged_results_and_merge_trains_spec.rb:53 Category:Continuous Delivery, ~"Merge Trains", QA, Quality, ~"S1", ~"bug", ~"devops::release", found:in MR, found:staging.gitlab.com, ~"group::progressive delivery"
Heatmap for ~missed-SLO bugs
| ~S1 | ~S2 | ~S3 | ~S4 | ~"No severity" | |
|---|---|---|---|---|---|
| ~P1 | 0 | 0 | 0 | 0 | 0 |
| ~P2 | 0 | 3 | 0 | 0 | 0 |
| ~P3 | 0 | 0 | 0 | 0 | 0 |
| ~P4 | 0 | 0 | 0 | 0 | 0 |
| ~"No priority" | 0 | 0 | 0 | 0 | 1 |
This is a group level triage package that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook: