Pipeline Execution 15.9 Planning issue
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
This issue is closed as of 2023-01-17
The Single Source of Truth (SSOT) for the status of issues in the milestone is the milestone board where issues are stack ranked by priority.
🎥
Recordings - Refinement Kickoff - Published 2022-12-19
- Group Kickoff - Published 2023-01-17
Theme/Focus for the milestone: Pipeline Performance and scale
Goals for the milestone
-
Meet Reliability issue SLOs - VerifyP1 issues -> Ensuring we have a reliable and stable platform maps to the GitLab Hosted First investment theme -
Move CancelPendingPipelines step to run async (gitlab-org/gitlab#383156 - closed) -
Partition ci_builds table (gitlab-org/gitlab#382033 - closed) -
Append `partition_id` to queries triggered thro... (gitlab-org/gitlab#377940 - closed)
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.
VerifyP1
-
Any VerifyP1 issues that carryover from the previous milestone. -
Confidential issue - https://gitlab.com/gitlab-org/gitlab/-/issues/372736
VerifyP2
Infradev Issues
Feature flags to be rolled out this milestone
-
Simplify token prefix/validation (gitlab-org/gitlab#385590 - closed) - issue and rollout -
Add issue here - link
Quality tests/Flaky tests to be resolved
-
Add issue here - link -
Add issue here - link
Docs improvement
-
Add issue here - link -
Add issue here - link
Issue Breakdown
As part of cross functional prioritization framework we track the % of issue types and weights in planning to forecast against the team's current needs.
This planning happens in a comment thread in the issue.
Designer/UX
- Epic: gitlab-org&5866
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 - Engineers have assigned ~deliverable
and~stretch
labels and have indicated commitment with a👍 or👎 on this 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
Edited by James Heimbuck