Milestone 17.3 review and discussion (Package stage)

(JUNE 20 - JULY 18)
Milestone 17.3 

- Resolve security vulnerabilities to ensure we continue to deliver on our SLAs.
- The container registry will be to GA (off-by-default) for self-managed customers by September 1st to increase the adoption of the next-gen registry by 10x.
- Continue development of an API-only Maven virtual registry to drive ARR
- Continue adding support for container registry background migrations to make deployments and upgrades easier.
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 three security vulnerabilities to resolve this milestone. We must continue to meet our SLAs.
Investigations
- Investigate: Maven allow/prevent duplicates fea... (#467254 - closed) customer
- Investigate relatively high p95 aggregated stor... (container-registry#1239 - closed) performance-refinement Engineering Time
- GitLab Rails Plan for "Allowing moving projects... (#435954 - closed)
Container Registry
This milestone we will continue to resolve issues that block GA self-managed for the registry. We'll also continue to make progress on background migrations, database load balancing, and using Redis as a cache.
- Document Downgrading Container Registry Version... (container-registry#1212 - closed)
- Importer: Reconsider the "Clean Database" Optio... (container-registry#943 - closed)
- container-registry#1265 (closed)
- DLB: Initial fault tolerance implementation (container-registry#1292 - closed) Engineering Time
- Use Redis repository cache for the tag list ope... (container-registry#803 - closed) Engineering Time
- Use Redis repository cache for the manifest dow... (container-registry#805 - closed) Engineering Time
- [container registry migration] Remove backend r... (#409873 - closed) Engineering Time
- Do not show (zero) size of container registry m... (#431048 - closed)
- Create alerts for webhook notification error tr... (container-registry#876 - closed) Engineering Time
- Add full test coverage for the async Background... (container-registry#1298 - closed)
- Enable sorting by published date for self-managed (#458822 - closed)
- Container registry list UI: Hide link to `Set u... (#463205 - closed)
Package Registry
_This milestone, we'll continue to work on an API-only Maven virtual registry. In addition, we'll make progress on the work required for Cells, as well as other performance and reliability improvements _
- Maven Virtual Registry: Maven API endpoint (#467982 - closed)
- Maven Virtual Registry: Cache logic (#467983 - closed)
- Maven Virtual Registry: Registry models API (#467979 - closed)
- Make "allow anyone to pull" work with group-lev... (#468059 - closed)
- Allow any GitLab user to search for public NuGe... (#467396 - closed)
- Keeping only 1 duplicated_package_files prevent... (#455041 - closed)
- Add sharding key for packages_dependencies table (#465276 - closed) Engineering Time
- Set sharding key for packages_composer_cache_fi... (#461786 - closed) Engineering Time
- Create a service to generate npm packages metad... (#463822)
- Show accurate number of errored packages on pac... (#460583 - closed)
Stretch goals
Stretch goals are good to work on between Deliverable issues.
- https://gitlab.com/gitlab-org/ci-cd/package-stage/package/-/issues/187+ Engineering Time
- Implement first iteration of (sync/CLI) BBM pro... (container-registry#1285 - closed)
- https://gitlab.com/gitlab-org/container-registry/-/issues/1223+
- chore(handlers): define counters interface to s... (container-registry#1300 - closed)
Product and Design issues
- https://gitlab.com/gitlab-org/ux-research/-/issues/3051+
- Problem validation: Package stage to add compon... (#466083 - closed)


Please order by From date
Person | From | To |
---|---|---|
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.