Skip to content

Pipeline Execution 17.9 Planning Issue

TODO - how to create this item

  • Title this issue Pipeline Execution X.Y Planning issue
  • Update Goals and theme for the issue. These roll up to larger OKRs the team is working on or large initiatives.
  • Add VerifyP1 issues Product would like to prioritize for release, these should contribute to the goals and theme
  • Add VerifyP2 issues that are secondary / Stretch goals or would further contribute to the theme and OKRs
  • Identify any Security, Infrastructure, Bug etc. issues that should prioritized per Global Prioritization
  • Delete this todo list

What's the focus, where can I find issue candidates for the milestone?

Issue Boards

PE workflow board | Issues by Team Member

Current/Upcoming Security issues

Recordings 🎥

  • Refinement Kickoff - TBD
  • Group Kickoff - TBD

Theme: Ultimate ARR Growth & CSAT

Goals for the milestone (consider OKR and Yearly Alignment)

  1. Start GitHub Integration MVC Implementation - okr
  2. Customer impacting bug fixes - okr

Issues of note

This is a breakdown of the issues in the milestone. For more information about how we prioritize check out the handbook page.

Open Security issues

Click to expand 
---
display: table
fields: title, assignees, weight, labels("bug::vulnerability"), labels("*SLO*"), due, labels("*end"),  labels("Verify::*"), labels("type::*"), milestone, labels("workflow::*"), labels
---
group = "gitlab-org" and label = "group::pipeline execution" and label = "security" and opened = true

Open Infradev issues

Click to expand 
---
display: table
fields: title, assignees, weight, labels("*end"), labels("*SLO*"), labels("Verify::*"), labels("type::*"), milestone, labels("workflow::*"), labels
---
group = "gitlab-org" and label = "group::pipeline execution" and label = "infradev" and opened = true

Candidate Non-Engineering Time

Click to expand 
---
display: table
fields: title, assignees, weight, labels("*end"), labels("type::*"), milestone, labels("workflow::*"), labels
---
group = "gitlab-org" and label = "group::pipeline execution" and label != "Engineering Time" and label = "candidate::17.9"

Engineering Time

Click to expand 
---
display: table
fields: title, assignees, weight, labels("*end"), labels("type::*"), milestone, labels("workflow::*"), labels
---
group = "gitlab-org" and label = "group::pipeline execution" and label = "Engineering Time" and label = "candidate::17.9"

Potential Carry-forward Issues

Click to expand 
---
display: table
fields: title, assignees, weight, labels("*end"), labels("type::*"), labels("Engineering Time", "Deliverable", "Stretch", "Spike"), labels("workflow::*"), milestone, labels
---
group = "gitlab-org" and label = "group::pipeline execution" and milestone = "17.8" and opened = true

Scheduled Issues

Click to expand 
---
display: table
fields: title, assignees, weight, labels("*end"), labels("type::*"), labels("Engineering Time", "Deliverable", "Stretch", "Spike"), labels("workflow::*"), milestone, labels
---
group = "gitlab-org" and label = "group::pipeline execution" and milestone = "17.9" and opened = true

Planning Tasks

  • PM highlights work for Deliverables, User Experience, Bug Fixes, Security Fixes, Technical Debt sections
  • PM describes how this milestone aligns with the company's OKRs
  • PM notes target percentages for cross functional prioritization
  • By 7th - DRI for milestone refinement assigns issues with ~needs weight label in ~workflow::planning breakdown to engineers for review ahead of the milestone kickoff.
  • By 11th - DRI for milestone refinement follows up with engineers about issues not in ~workflow::read for development
  • By 14th - EM assigns any unassigned issues in the milestone
  • By 16th - The team has discussed potential ~Deliverable and ~Stretch labels and have indicated commitment with a 👍 or 👎 in the planning issue.
  • By 19th - EM reviews ~deliverable and ~stretch labels to assigned to issues.
  • By 19th - EM ensures all issus are assigned.
  • EM / PM remove any remaining issues form ~workflow::planning breakdown
  • Engineers begin working on issues in workflow::ready for development

Reference for How We Plan

Edited by Rutvik Shah