Milestone 15.5 review and discussion

Milestone 15.5 🚀

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

Holidays 🌴

🗓 Shared calendar

Please order by From date

Person	From	To
Rahul	September 22	September 22
F&F Day	September 26	September 26
F&F Day	October 10	October 10
Tim	July 25	September 16
Sofia	September 14	September 22
Jaime	September 17	September 26

Capacity 📦

Say/Do dashboard

Past 3 milestone commitments 🕰

Milestone	Deliverable issues planned	Deliverable issues delivered	Deliverable issues rescheduled	Average weight	Total weight
15.5	21			1.80	38
15.4	24			1.79	43
15.3	17			1.41	24

Goals 🎯

What are we doing, and why is it important?

1. The number one goal is for container registry performance and scalability. For example, continuing integrating Redis and auto-deployments.
2. The second goal is to resolve a bug with the container registry UI, which is limiting the number of tags displayed to 100.
3. The third goal is to break ground on the Maven request forwarding feature which is a key first step towards a maven virtual registry.
4. Support contractor to work on RPM support.

P1 (Deliverable) Issues 🦊

Please remember to make time in each milestone for learning and personal projects in addition to the below list.

Security Issues

By prioritizing security-related issues, we can help reduce GitLab's threat landscape by:

• Reducing the likelihood of breach
• Reducing the exposure and severity of vulnerabilities
• Reducing the cost associated with service vulnerabilities

PLACEHOLDER, AT THE MOMENT WE DON'T HAVE ANY security ISSUES TO PRIORITIZE.

Container Registry

With the migration almost done, we should shift the focus for the Registry to scalability, performance, and data instrumentation. For scalability and performance, I'd like to continue to work on auto-deployments and start working on active database loadbalancing. For instrumentation, I'd like to continue with the investigation into adding user level data and how to implement data transfer usage data.

1. Complete migration
   1. Migrate gitlab-org to the new registry
   2. Migrate Very Large Repositories
   3. Import VIP Repositories Affected by #744
   4. Migrate repositories served by the old path
2. Data transfer visibility for the container registry
   1. Build an implementation for data transfer instrumentation
   2. Add ability to filter on authentication token type to Registry logs
3. Active database loadbalancing
   1. Support rollout of Redis to cache database repository objects in pre
   2. Build an implementation plan for Container Registry active database load balancing
4. Refactor notification system
   1. Add conformance tests for the notification system
   2. Define a queue interface for the new notification system
5. Performance improvements for cleanup policies
   1. Introduce a switch (based on the repository migration status) rails
   2. Rollout (feature-flag) 🇳🇵 rails
6. Do not show "cleanup policies are disabled at admin level" notification while page is loading frontend
7. Create release issue using the CI

Package Registry

For the Package Registry, I'd like to focus on providing accurate storage data, Maven request forwarding project and key improvements for npm

1. Investigate incorrect statistics for packages
2. Maven request forwarding
   1. Cascading namespace settings for package forwarding
   2. Cascade package forward settings from admin area to group frontend
3. Create a service to marks many packages for destruction
4. GraphQL mutation for bulk deletion of packages
5. Add last_downloaded date to the Package Registry UI frontend
6. Improve modal copy when deleting either the last or package files frontend
7. Test RPM package manager push/pull
8. Test Maven request forwarding

Community Contributions

In 15.4, an external contractor started to add support for RPM to the Package Registry. If it goes well, we can work with them in the future to add support for more formats.

1. RPM support
2. Feature specific permissions for the Package Registry

Stretch goals

Container Registry:

1. Attach a notification queue to the App handlers
2. Container Registry is only showing 100 tags per image typebug rails
3. Registry cleanup policy GraphQL endpoints SUSImpacting rails

Package Registry:

1. Some NPM packages published in multiple projects are inaccessible typebug
2. CI_JOB_TOKEN for npm does not work with dependencies typebug
3. Put call to action to answer survey about Artifactory migration in product UI

Dependency Proxy:

1. Dependency proxy image pull failures for pipelines triggered by project access tokens typebug

Quality & quad-planningcomplete-action

Reviewed issues with actions:

Issue Refinement

Each milestone we want to ensure that we allow time to review, discuss, and weight issues. The goal is to ensure that the issue is ready for development before planning it for a given milestone.

1. https://gitlab.com/gitlab-org/ci-cd/package-stage/package/-/issues/102+

Research

Issue	Deliverable
Package Touchpoint research	Record 3 customer interviews

Design

Design work for this milestone is captured on design issue.

Kick-off video 🎥

1. GitLab 15.5 Kickoff - Package:Package