2020-11-02 - Triage report for "group::package"
Hi, @trizzi @jhampton @icamacho
This is a group or stage level triage report 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)
- gitlab-org/gitlab#271534 (closed) Generic Package download should not require authentication on public projects devopspackage, ~"feature", ~"group::package", needs investigation, sectionops
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.
- Engineering Managers: Please add a severity label for those issues without one
- Product Designers: Please add a severity label to UX ~bug issues without one
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.
| severity1 | severity2 | severity3 | severity4 | No severity | |
|---|---|---|---|---|---|
| priority1 | 0 | 0 | 0 | 0 | 0 |
| priority2 | 0 | 13 | 0 | 0 | 0 |
| priority3 | 0 | 1 | 27 | 1 | 0 |
| priority4 | 0 | 1 | 7 | 11 | 0 |
| No priority | 0 | 0 | 20 | 1 | 32 |
Unscheduled ~bug with customer
- gitlab-org/gitlab#273427 Some NPM packages published in multiple projects are inaccessible ~"Accepting merge requests", Category:Package Registry, ~"NPM Registry", backend, ~"bug", customer, devopspackage, ~"group::package", ruby, sectionops, severity3
Unscheduled ~bug (non-customer)
- gitlab-org/gitlab#273697 (closed) Unable to restore NuGet packages with 4 digit version number and last digit is 0 ~"bug", devopspackage, ~"group::package", priority2, sectionops, severity2
- gitlab-org/gitlab#273034 (closed) Generic Package Repository not allowing SemVer with a label (1.0.0-beta, 1.0.0-rc1, etc.) Category:Package Registry, ~"bug", devopspackage, ~"group::package", sectionops, severity3
Heatmap for ~missed-SLO bugs
| severity1 | severity2 | severity3 | severity4 | No severity | |
|---|---|---|---|---|---|
| priority1 | 0 | 0 | 0 | 0 | 0 |
| priority2 | 0 | 9 | 0 | 0 | 0 |
| priority3 | 0 | 1 | 0 | 0 | 0 |
| priority4 | 0 | 1 | 0 | 0 | 0 |
| No priority | 0 | 0 | 0 | 0 | 0 |
Heatmap for vintage bugs
| severity1 | severity2 | severity3 | severity4 | No severity | |
|---|---|---|---|---|---|
| priority1 | 0 | 0 | 0 | 0 | 0 |
| priority2 | 0 | 0 | 0 | 0 | 0 |
| priority3 | 0 | 0 | 4 | 0 | 0 |
| priority4 | 0 | 0 | 1 | 2 | 0 |
| No priority | 0 | 0 | 0 | 0 | 0 |
This is a group level triage report that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook:
If assignees or people mentioned in this individual triage report need to be amended, please edit group-definition.yml.
Activity
added grouppackage registry triage report labels
Setting label(s) devopspackage sectionops based on ~"group::package".
added devopspackage sectionops labels