Milestone 17.7 review and discussion (Package stage)

Milestone 17.7 🚀 (NOV 21 - DEC 19)

Goals

  1. Prepare the container registry for GA by default to help drive the adoption of the next-generation container registry.
  2. Continue to add support for database load balancing and background migrations to improve the container registry's reliability, performance, and observability.
  3. Continue to advance the Maven virtual registry by resolving technical debt and finalizing the documentation.
  4. Roll out the protected container images feature to improve the security of Package products.
  5. Add a new scope to GitLab tokens for the dependency proxy for containers.
  6. Investigate the possibility of adding the GitLab package registry to the global search for improved usability and performance.

🛡️ Security issues

Open issues

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

group="gitlab-org" and milestone = "17.7" 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.7" 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.7" 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.7" 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.7" 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.7" 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.7" 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.7" 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.7" and label = ("devops::package", "Package:P2")

Product and Design issues

---
display: table
fields: title, epic, assignees, healthStatus, state
---

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

Kick-off video 🎥

GitLab 17.7 Kickoff - Package:Package

Holidays 🌴

🗓️ Shared calendar

Please order by From date

Person From To

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.
Edited by Jaime Martinez