2020-08-31 - 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.
feature (non-customer)
Unscheduled- #243445 (closed) Remove stale packages/_legacy_package_list.html.haml Category:Package Registry, QA, devopspackage, feature, ~"feature::maintenance", frontend, ~"group::package"
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.
severity1 | severity2 | severity3 | severity4 | No severity | |
---|---|---|---|---|---|
priority1 | 0 | 0 | 0 | 0 | 0 |
priority2 | 0 | 7 | 0 | 0 | 0 |
priority3 | 0 | 1 | 26 | 0 | 0 |
priority4 | 0 | 1 | 6 | 14 | 0 |
No priority | 0 | 7 | 14 | 0 | 23 |
Unscheduled ~bug (non-customer)
- #241678 (closed) Unable to install python package via pip from pypi repository if package has period in its name PyPI Repository, ~"bug", devopspackage, ~"group::package", sectionops, severity3
- #241494 Can't download/install pypi package form the package registry ~"bug", devopspackage, ~"group::package", sectionops, severity2
- #241492 (closed) Can't upload pypi package - 500 Internal Server Error ~"bug", devopspackage, ~"group::package", sectionops, severity2
-
#240897 (closed) Group deploy tokens with
read_package_registry
scope do not grant access to the Composer Package registry Composer Repository, backend, ~"bug", devopspackage, ~"group::package", ruby, sectionops, severity3 - #240887 (closed) Packages/composer: semver not fully supported Category:Container Registry, ~"bug", devopspackage, ~"group::package", severity3
- #239258 (closed) Sidekiq job Packages::Nuget::ExtractionWorker causes sidekiq to error out when fed bad version data Category:Package Registry, NuGet Repository, backend, ~"bug", devopspackage, ~"group::package", sectionops
- #223074 (closed) (confidential) ~"(confidential)"
- #222843 (confidential) ~"(confidential)"
Heatmap for ~missed-SLO bugs
severity1 | severity2 | severity3 | severity4 | No severity | |
---|---|---|---|---|---|
priority1 | 0 | 0 | 0 | 0 | 0 |
priority2 | 0 | 6 | 0 | 0 | 0 |
priority3 | 0 | 0 | 0 | 0 | 0 |
priority4 | 0 | 0 | 0 | 0 | 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.