Milestone 17.4 review and discussion (Package stage)

(AUG 16 - SEP 19)
Milestone 17.4 

- Resolve security vulnerabilities to ensure we continue to deliver on our SLAs.
- Drive adoption of the next-gen container registry by moving to GA and making more features available for self-managed customers.
- Advance GitLab's Maven virtual registry in preparation for a 17.5/6 Beta release.
- Begin to build a download counter for the container registry to help Platform Engineers better understand how the content in their registry is being used and to help developers trust the container images they are using.
P1 (Deliverable) Issues 

Stretch goals
Stretch goals are good to work on between Deliverable issues.
Category | Issue | Why it's important | Labels |
---|---|---|---|
Container registry | Add health probe for database | Performance | golang Engineering Time |
Package registry | Make "allow anyone to pull" work with group-level Maven endpoints | Usability | rails |
Team efficiency | Automated news feed | Efficiency | rails |
Product and Design issues
Category | Issue | Why it's important | Labels |
---|---|---|---|
Package and container registry | User research about registry usage data | Understand what's important for users | workflowproblem validation |
Package registry | Review npm registry docs | documentation | |
Team efficiency | Automated news feed | Efficiency | rails |

- GitLab 17.4 Kickoff - Package:Package

Please order by From date
Person | From | To |
---|---|---|
@10io | 2024-09-14 | 2024-09-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.