Milestone 18.10 review and discussion (Package Stage)

Milestone 18.10 🌷 (Feb 16 - Mar 13)

Goals

In 18.10, we continue advancing virtual registries and the Unified Artifact Management initiative. We'll also continue progress on Docker, npm and Maven virtual registries, advance the Container Registry self-managed database rollout, and maintain our focus on bug burndown and system reliability.

  1. 🚀 Advance the Product Roadmap
  2. ⏰ Vulnerabilities with upcoming due dates
  3. 🤝 Progress Geo/Protocells dependencies
  4. 🧯 Burn down our bug backlog
  5. ⚙️ Improve stability and reliability of our products
    • Improve Observability and Usage metrics 📈

❗ Vulnerabilities - High Priority 

---
display: table
fields: title, assignees, labels("workflow::*"), state, weight, labels("group::*")
---

group="gitlab-org" and milestone = "18.10" and label = ("bug::vulnerability", "devops::package")

🚢 Container registry

Open issues 

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

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

Unified Artifact Management

Open issues 

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

group="gitlab-org" and milestone = "18.10" and state = opened and label = ("devops::package") and epic = 19844

Closed issues 

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

group="gitlab-org" and milestone = "18.10" and state = closed and label = ("devops::package") and epic = 19844

Bug Burndown

Open issues 

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

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

Closed issues 

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

group="gitlab-org" and milestone = "18.10" 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.10" 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.10" and label = ("devops::package", "UX") and label in ("workflow::problem validation", "workflow::solution 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
@10io 2026-02-18 2026-02-20

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 need refinement

Operational tasks

  1. PM: Create this issue with the title "Milestone XX.Y review and discussion (Package stage)"
  2. EM: Assign the issue to PM, EM, and PD
  3. EM: Set the due date to the end of the milestone
  4. EM: Update GLQL with the correct milestone
  5. EM: Write goals, list deliverables, community contribution, and stretch issues that align with the goals
  6. PM: Review the teams goals for alignment with Product direction
  7. EM: Change the milestone on carryover issues from the previous milestone plan
  8. EM: Start a discussion thread with project DRIs to add upcoming issues
  9. PD: List usability improvement issues
  10. PM: List research issues
  11. EM: List issues needing refinement
  12. 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 refine them
  13. EM: For issues that are refined and labeled as Package:P1, assign Deliverable
  14. EM: Confirm the list of issues in this issue match with the ones in the filter.
  15. 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.
  16. PM: Record the kickoff video, link to this issue, and share it on Slack.
  17. EM: On the first day of the milestone record the number of issues completed in the previous milestone closed and the number of issues scheduled in the current milestone (deliverable + stretch).
Edited by David Fernandez