18.7 Planning issue

Internal Milestone 18.7 Review & Discussion 🚀

Milestone	Code Cut-off
18.7	2025-12-12

PTOs

PTOs for 18.7:

• @cipherboy-gitlab - 5 days
• @ken.mcdonald - 2 days
• @mgandres - 1 day
• @iamricecake - 1 day
• @dbiryukov - 2 days
• @ahuntsman - 2 days

Milestone Issues 🦊

backend

---
display: table
fields: title, weight, labels("type::*"), labels("missed:*")
---
project = "gitlab-org/gitlab" AND
milestone = "18.7" AND
state = opened AND
label = ("group::pipeline security", "backend")

Total backend weight: X

frontend

---
display: table
fields: title, weight, labels("type::*"), labels("missed:*")
---
project = "gitlab-org/gitlab" AND
milestone = "18.7" AND
state = opened AND
label = ("group::pipeline security", "frontend")

Total frontend weight: X

Issues scheduled for %Next 1-3 releases

---
display: table
fields: title, weight, labels("type::*"), milestone
---
project = "gitlab-org/gitlab" AND
milestone = "Next 1-3 releases" AND
state = opened AND
label = ("group::pipeline security")

Ratios

Let's add up the issue types we have based on my recommended plans for frontend and backend, so that we can see what our balance is.

Issue Type	Total Issues	Total Weight	Percentage for Count	Percentage for Weight
typefeature	X	X	X%	X%
typebug	X	X	X%	X%
typemaintenance	X	X	X%	X%

User experience 🎢

Item	Issue	Weight	Type
1	Issue	X	type
2	Issue	X	type
3	Issue	X	type
4	Issue	X	type

Planning Tasks

• By the third Tuesday of the month - EM/PM highlights work for Deliverables, highlighting Bug Fixes, Security Fixes, Technical Debt sections and pings team for review
• By the third Tuesday of the month - UX highlights work for User Experience section
• 2 days prior to milestone start - EM applies ~Deliverable, ~"Govern::P1", and other applicable labels for the new milestone
• First day of the milestone - Engineers begin working on issues in workflow::ready for development