Milestone 18.2 review and discussion (Package Stage)

Draft: Milestone 18.2 🚀 (June 13 - July 11)

Goals

1. 🚀 Advance the Product Roadmap
   • grouppackage registry Maven virtual registry
   • groupcontainer registry Container image virtual registry
   • groupcontainer registry Self-Managed Database Deployment and Migration
2. ⚙️ Improve stability and reliability of our products
   • grouppackage registry Test improvements
   • groupcontainer registry Database load balancing
   • groupcontainer registry API Rate Limiting
   • groupcontainer registry Storage driver improvements
3. ⏩ On-going projects
   • grouppackage registry Packages table decomp
   • groupcontainer registry Release process improvements
   • grouppackage registry Dependency proxy improvements
4. 🧯 Burn down our bug backlog

🚢 Container registry

Open issues

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

group="gitlab-org" and milestone = "18.2" 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.2" 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.2" 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.2" 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.2" 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.2" and state = closed and label = ("Category:Virtual Registry", "Package:P1")

Bug Burndown

Open issues

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

group="gitlab-org" and milestone = "18.2" and state = opened and label = ("type::bug", "devops::package")

Closed issues

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

group="gitlab-org" and milestone = "18.2" and state = closed and label = ("type::bug", "devops::package")

Stretch

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

group="gitlab-org" and milestone = "18.2" 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.2" and label = ("devops::package", "UX") and label in ("workflow::problem validation", "workflow::solution validation", "workflow::ready for design", "workflow::design", "workflow::in review", "workflow::planning breakdown")

Holidays 🌴

🗓️ Shared calendar

Please order by From date

Person	From	To	Coverage Issue (if required)
@adie.po	Jun 16	Jun 19
@crystalpoole	Jun 19	Jul 6	https://gitlab.com/gitlab-com/engineering-division/pto-coverage/-/issues/169+
@adie.po	Jun 30	Jul 10
@10io	Jun 19	Jul 2	https://gitlab.com/gitlab-com/engineering-division/pto-coverage/-/issues/182+s

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.