Pipeline Execution 18.0 Planning issue

TODO - how to create this item

  • Title this issue Pipeline Execution X.Y Planning issue
  • Replace with the milestone and <last_milestone> with previous milestone values in glql blocks
  • 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

Recordings 🎥

  • Refinement Kickoff - TBD
  • Group Kickoff - TBD

Theme: Pipeline QoL improvements

Goals for the milestone (consider OKR and Yearly Alignment)

  1. Fix Security and InfraDev issues
  2. Make RCA available for Duo Premium
  3. Create an implementation plan for Streamline artifact handling for child/parent p... (gitlab-org&4019) • Max Fan

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 Vulnerability 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("Verify::*"), labels("type::*"), milestone, labels("workflow::*"), labels
---
group = "gitlab-org" and label = "group::pipeline execution" and label != "Engineering Time" and label = "candidate::18.0" and opened = true

Candidate 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::18.0" and opened = true

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.11" 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 = "18.0" and opened = true

Planning Tasks

Click to expand
  • PM updates list of candidate Issues (Non-Engineering Time)
  • EM updates list of candidate Engineering Time Issues
  • PM describes how this milestone aligns with the company's OKRs
  • By 2 weeks before previous milestone cut-off EM tags Engineers in planning issue
  • By Friday, 1 week before previous milestone cut-off Engineers complete planning task lists.
  • By Monday of release week - EM reviews ~deliverable and ~stretch labels to assigned to issues.

Reference for How We Plan

Edited by Rutvik Shah