2019-09-16 - 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.
Unscheduled feature (non-customer)
-
#31517 Make composable Auto DevOps elements easy to find and use Category:Continuous Delivery, ~"auto devops", ~"devops::release", direction, 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 | 7 | 0 | 0 | 0 |
| ~P3 | 0 | 0 | 9 | 0 | 0 |
| ~P4 | 0 | 0 | 0 | 6 | 0 |
| ~"No priority" | 0 | 0 | 0 | 0 | 3 |
Unscheduled ~bug (non-customer)
-
#28821 (closed) Merge train missing status information to be usable Category:Continuous Delivery, ~"bug", ~"devops::release", ~"devops::release::merge trains", ~"group::progressive delivery" -
#31726 (closed) Review app visual review toolbar detects Edge as Chrome Category:Review Apps, ~"bug", ~"devops::release", ~"group::progressive delivery" -
#29849 (closed) Readiness probe failed: Get http://10.244.2.186:5000/: dial tcp 10.244.2.186:5000: connect: connection refused Back-off restarting failed container Category:Continuous Delivery, ~"Release [DEPRECATED]", ~"bug", ~"devops::release", ~"group::progressive delivery", support request
Heatmap for ~missed-SLO bugs
| ~S1 | ~S2 | ~S3 | ~S4 | |
|---|---|---|---|---|
| ~P1 | 0 | 0 | 0 | 0 |
| ~P2 | 0 | 2 | 0 | 0 |
| ~P3 | 0 | 0 | 0 | 0 |
| ~P4 | 0 | 0 | 0 | 0 |
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: