Milestone 18.0 review and discussion (Package Stage)

Milestone 18.0 🚀 (Apr 11 - May 9)

Goals

1. Security Issues: Maintain our commitment to security by meeting SLA requirements and addressing security concerns promptly to ensure our product remains trustworthy and protected.
2. Breaking Changes: Deploy necessary breaking changes behind feature flags, ensuring a smooth transition for users during the upgrade.
3. Maven Virtual Registry: Complete the development and documentation of the Maven virtual registry and add multi-upstream support capabilities to support the Beta release of this critical feature.
4. Security and Compliance Features: Implement immutable tags as our first Ultimate tier feature.
5. Expand the dependency proxy for containers to work with private Docker Hub accounts and evaluate how it can support other popular container registries, such as ECR, Quay, Google Artifact Registry, Quay, and Harbor.
6. Customer Bug Fixes: Address specific user-reported issues
7. 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.

❗ Breaking changes

Open issues

---
display: table
fields: title, epic, assignees, labels("workflow::*"), healthStatus, weight, labels("Rails", "Golang", "frontend")
---

group="gitlab-org" and milestone = "18.0" and milestone = "17.11" and state = opened and label = ("devops::package", "breaking change")

Closed issues

---
display: table
fields: title, epic, assignees, labels("workflow::*"), healthStatus, weight, labels("Rails", "Golang", "frontend")
---

group="gitlab-org" and milestone = "18.0" and milestone = "17.11" and state = closed and label = ("devops::package", "breaking change")

🛡️ Security issues

Open issues

---
display: table
fields: title, epic, assignees, labels("workflow::*"), healthStatus, weight, labels("Rails", "Golang", "frontend")
---

group="gitlab-org" and milestone = "18.0" and state = opened and label = ("bug::vulnerability", "Package:P1")

Closed issues

---
display: table
fields: title, epic, assignees, labels("workflow::*"), healthStatus, weight, labels("Rails", "Golang", "frontend")
---

group="gitlab-org" and milestone = "18.0" and state = closed and label = ("bug::vulnerability", "Package:P1")

🚢 Container registry

Open issues

---
display: table
fields: title, epic, assignees, labels("workflow::*"), healthStatus, weight, labels("Rails", "Golang", "frontend")
---

group="gitlab-org" and milestone = "18.0" and state = opened and label = ("Category:Container Registry", "Package:P1")

Closed issues

---
display: table
fields: title, epic, assignees, labels("workflow::*"), healthStatus, weight, labels("Rails", "Golang", "frontend")
---

group="gitlab-org" and milestone = "18.0" and state = closed and label = ("Category:Container Registry", "Package:P1")

📦 Package registry

Open issues

---
display: table
fields: title, epic, assignees, labels("workflow::*"), healthStatus, weight, labels("Rails", "Golang", "frontend")
---

group="gitlab-org" and milestone = "18.0" and state = opened and label = ("Category:Package Registry", "Package:P1")

Closed issues

---
display: table
fields: title, epic, assignees, labels("workflow::*"), healthStatus, weight, labels("Rails", "Golang", "frontend")
---

group="gitlab-org" and milestone = "18.0" and state = closed and label = ("Category:Package Registry", "Package:P1")

Virtual registry

Open issues

---
display: table
fields: title, epic, assignees, labels("workflow::*"), healthStatus, weight, labels("Rails", "Golang", "frontend")
---

group="gitlab-org" and milestone = "18.0" and state = opened and label = ("Category:Virtual Registry", "Package:P1")

Closed issues

---
display: table
fields: title, epic, assignees, labels("workflow::*"), healthStatus, weight, labels("Rails", "Golang", "frontend")
---

group="gitlab-org" and milestone = "18.0" and state = closed and label = ("Category:Virtual Registry", "Package:P1")

Stretch

---
display: table
fields: title, epic, assignees, labels("category:*"), labels("workflow::*"), healthStatus, state, weight, labels("Rails", "Golang", "frontend")
---

group="gitlab-org" and milestone = "18.0" and label = ("devops::package", "Package:P2")

Product and Design issues

---
display: table
fields: title, epic, assignees, labels("workflow::*"), healthStatus, state
---

group="gitlab-org" and milestone = "18.0" and label = ("devops::package", "workflow::problem validation")

Holidays 🌴

🗓️ Shared calendar

Please order by From date

Person	From	To
@dmeshcharakou	April 11	Apr 21
@radbatnag	April 16th	April 18th
@10io	April 18th	April 21st
@radbatnag	April 28th	April 28th
@adie.po	May 2nd	May 2nd
@suleimiahmed	May 5th	May 9th
@adie.po	May 5th	May 9th

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

1. PM: Create this issue with the title "Milestone XX.Y review and discussion (Package stage)"
2. PM: Assign the issue to PM, EM, SET, and PD
3. PM: Set the due date to the end of the milestone
4. PM: Update GLQL with the correct milestone
5. PM: Write goals, list deliverables, community contribution, and stretch issues that align with the goals
6. SET: List quality issues
7. PD: List usability improvement issues
8. PM: List research issues
9. EM: List issues needing refinement
10. 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
11. EM: For issues that are refined and labeled as Package:P1, assign Deliverable and ~"Track Health Status" labels
12. EM: Confirm the list of issues in this issue match with the ones in the filter.
13. 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.
14. EM: Record a comment like this with the total weight, average, and type of issues ratio and update the table in this issue
15. PM: Record the kickoff video, link to this issue, and share it on Slack.