Milestone 17.10 review and discussion (Package stage)
Milestone 17.10 🚀 (FEB 20 - MAR 20)
Goals
- Security Issues: Maintain our commitment to security by meeting SLA requirements and addressing security concerns promptly to ensure our product remains trustworthy and protected.
- Breaking Changes: Prepare for GitLab 18.0 by implementing all necessary breaking changes behind feature flags, ensuring a smooth transition for users during the upgrade.
- Maven Virtual Registry MVC: Complete the development and documentation of the Maven virtual registry and plan for future milestones by investigating multi-upstream support capabilities.
- Security and Compliance Features: Enhance security controls through protected container tags, implement immutable tags as our first Ultimate tier feature, and begin exploring dependency firewall capabilities to strengthen package security.
- Usability Improvements: Enhance the user experience by refining settings layouts, optimizing the package registry list page, and preparing the creation of a new container registry tags details page.
- Customer Bug Fixes: Address specific user-reported issues, including Terraform sorting problems and npm override bugs, and investigate container registry Sentry alerts to improve platform stability.
- Container Registry Enhancements: Focus on three critical infrastructure improvements - implementing database load balancing, adding support for background migrations, and transitioning the next-generation container registry to GA status for GitLab 18.0.
🛡️ Security issues
Open issues
---
display: table
fields: title, epic, assignees, healthStatus, weight, labels("Rails", "Golang", "frontend")
---
group="gitlab-org" and milestone = "17.10" and opened = true and label = ("bug::vulnerability", "Package:P1")Closed issues
---
display: table
fields: title, epic, assignees, healthStatus, weight, labels("Rails", "Golang", "frontend")
---
group="gitlab-org" and milestone = "17.10" and closed = true and label = ("bug::vulnerability", "Package:P1")
🚢 Container registry
Open issues
---
display: table
fields: title, epic, assignees, healthStatus, weight, labels("Rails", "Golang", "frontend")
---
group="gitlab-org" and milestone = "17.10" and opened = true and label = ("Category:Container Registry", "Package:P1")Closed issues
---
display: table
fields: title, epic, assignees, healthStatus, weight, labels("Rails", "Golang", "frontend")
---
group="gitlab-org" and milestone = "17.10" and closed = true and label = ("Category:Container Registry", "Package:P1")
📦 Package registry
Open issues
---
display: table
fields: title, epic, assignees, healthStatus, weight, labels("Rails", "Golang", "frontend")
---
group="gitlab-org" and milestone = "17.10" and opened = true and label = ("Category:Package Registry", "Package:P1")Closed issues
---
display: table
fields: title, epic, assignees, healthStatus, weight, labels("Rails", "Golang", "frontend")
---
group="gitlab-org" and milestone = "17.10" and closed = true and label = ("Category:Package Registry", "Package:P1")Virtual registry
Open issues
---
display: table
fields: title, epic, assignees, healthStatus, weight, labels("Rails", "Golang", "frontend")
---
group="gitlab-org" and milestone = "17.10" and opened = true and label = ("Category:Virtual Registry", "Package:P1")Closed issues
---
display: table
fields: title, epic, assignees, healthStatus, weight, labels("Rails", "Golang", "frontend")
---
group="gitlab-org" and milestone = "17.10" and closed = true and label = ("Category:Virtual Registry", "Package:P1")Stretch
---
display: table
fields: title, epic, assignees, healthStatus, state, weight, labels("Rails", "Golang", "frontend")
---
group="gitlab-org" and milestone = "17.10" and label = ("devops::package", "Package:P2")Product and Design issues
---
display: table
fields: title, epic, assignees, healthStatus, state
---
group="gitlab-org" and milestone = "17.10" and label = ("devops::package", "workflow::problem validation")
Kick-off video 🎥
GitLab 17.10 Kickoff - Package:Package
Holidays 🌴
Please order by From date
| Person | From | To |
|---|---|---|
| @suleimiahmed | March 3rd | March 14th |
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 GLQL with the correct milestone -
PM: Write goals, list deliverables, community contribution, and stretch issues that align with 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.
Edited by Tim Rizzi