Milestone 17.0 review and discussion (Package stage)

(APR 18 - MAY 16)
Milestone 17.0 

- Deliver all breaking changes with minimal customer issues.
- Improve the performance of the Maven dependency proxy.
- Add the last published date and allow users to sort by it to make it easier to find and validate images/tags.
- Unblock self-managed customers from migrating to the new container registry.
- Improve the performance and reliability of the container registry.
P1 (Deliverable) Issues 

Please remember to make time in each milestone for learning and personal projects in addition to the below list.
Security Issues
We have one security vulnerability to resolve this milestone which is blocked by one of the breaking changes. So, we'll need to plan the work and release accordingly.
Breaking changes
Milestone 17.0 is a major milestone and includes seven breaking changes for the Package stage.
- Remove DELETE /v2/<name>/tags/reference/<tag> A... (container-registry#1095 - closed)
- Removal: container registry `List registry repo... (#439916 - closed)
- Raise the permissions of the group-level APIs t... (#370471 - closed)
- Removal: Package pipelines in API payload shoul... (#289956 - closed)
- Migrate packages and registries graphql to add ... (#390754 - closed)
- Change the npm package upload from sync to async (#433009 - closed)
- Dependency Proxy: add group access scope checks... (#431386)

_This milestone we have several investigations planned. The first item listed is a corrective action after a production incident in %16.11. The others are investigating the container registry's performance or the Maven dependency proxy.
- Corrective action: Investigate why HTTP/2 reque... (gitlab-com/gl-infra/production-engineering#25230 - closed) corrective action
- Investigate the performance of the repositories... (#444463)
- Review queries in container_repository_details_... (#454060 - closed)
- Investigate dependency proxy for packages perfo... (#451242 - closed)
Container Registry
_This milestone, we have some exciting issues planned. We'll add the last published date and the ability to sort by that date into the UI! We'll also resolve bugs and add documentation to help drive the adoption of the metadata database. We also have work scheduled for the public preview of the Artifact Management Integration.
- fix(notifications): retrying sink does not stop... (container-registry#1210 - closed)
- Document three-step migration process for Helm ... (#439684 - closed)
- Build an implementation plan for Container Regi... (container-registry#770 - closed)
- GCP Integration: consolidate GCP jwt implementa... (#435739 - closed)
- Consolidate guards around list and details oper... (#443518 - closed)
- Display the last published date for container r... (#290949 - closed)
- Sort the container registry tags list by publis... (#351031 - closed)
- Validate JWT issued for moving a project within... (container-registry#1176 - closed)
- Move the Harbor integration from `Operate` to `... (#439494 - closed)
- Use Redis repository cache for the list reposit... (container-registry#802 - closed)
- https://gitlab.com/gitlab-org/container-registry/-/issues/1222+
- [container registry migration] Remove backend r... (#409873 - closed)
- Improve handling of timeout bursts during onlin... (container-registry#1238 - closed)
- Reduce container width of GAR list and image de... (#454835 - closed)
Package Registry
This milestone, we'll focus on resolving bugs with the dependency proxy for packages, adding the Terraform README.md, and improving the UX of the package registry page. If we have the bandwidth, we'll also prioritize npm dependency proxy work.
- Dependency proxy: some files will interrupt the... (#448886 - closed)
- Filter package registry UI to show packages wit... (#451054 - closed)
- Maven dependency proxy: upstream url with a tra... (#452046 - closed)
- Pypi package upload errors due to violation of ... (#444304 - closed)
- Integrate the Terraform README into the respons... (#438059 - closed)
- Create Conan package class (#435825 - closed)
Stretch goals
Stretch goals are good to work on between Deliverable issues.
- Package: Package Registry Group documentation u... (#443450 - closed)
- Package: Container Registry Group documentation... (#443449 - closed)
- Package Registry pagination returns empty resul... (#448716 - closed)
- Refactor Package Registry QA Specs to Improve R... (#454608)
- Container Registry - Investigate and fix test f... (#454609 - closed)
Research issues


Please order by From date
Person | From | To |
---|---|---|
@trizzi | May 10 | May 21 |
Helpful links
Helpful links | Use this for |
---|---|
Functional breakdown | Viewing issues scheduled for the current and next several milestones. |
Milestone board | See how the planned issues are broken down by function. |
Workflow board | See how the milestone issues are broken down by their current status (workflow). |
List of P1 unweighted issues | A list of issues that are not yet weighted, which is a requirement for P1 issues. |
Issues that need refining | A list of issues that refinement |
Issue types by milestone | See the ratio of features, maintenance, and bugs |
Operational tasks
- PM: Create this issue with the title "Milestone XX.Y review and discussion (Package stage)"
- PM: Assign the issue to PM, EM, SET, and PD
- PM: Set the due date to the end of the milestone
- PM: Update links with the correct milestone
- PM: Write goals, list deliverables, community contribution, and stretch issues that align to the goals
- SET: List quality issues
- PD: List usability improvement issues
- PM: List research issues
- EM: List issues needing refinement
- EM: Review that all issues listed as deliverables are refined. If there is missing weight, implementation plan, and/or workflowready for development label, then ping the team to perform refinement
- EM: For issues that are refined and labeled as Package:P1, assign Deliverable and ~"Track Health Status" labels
- EM: Confirm the list of issues in this issue match with the ones in the filter.
- EM: Confirm there is enough work for golang engineers, rails engineers, and frontend engineers, and capacity is not exceeded. Can use the functional breakdown board to evaluate weights and coordinate with the team to confirm they feel comfortable with the commitments.
- EM: Record a comment like this with the total weight, average, and type of issues ratio and update the table in this issue
- PM: Record the kickoff video, link to this issue, and share it on Slack.
This issue was generated using the Package:Package Registry milestone plan template.