Skip to content

Code Review 18.3 Planning : July

Release planning for the Code Review Group

Overview - 18.3 Release Board

Backend

Planning distribution

Priorities

  1. Milestone dedicated to the Engineering Allocation, see https://gitlab.com/gitlab-org/gitlab/-/issues/552074 and https://gitlab.com/gitlab-com/create-stage/create-engineering-managers/-/issues/845

Frontend

Planning distribution

Priorities

Issues scheduled for 18.3

display: table
fields: epic, title, assignee, weight, labels("type::*", "backend", "frontend")
title: Unassigned issues ~backend / ~frontend  (should be empty by the end of planning)
collapsed: true
query:
  group = "gitlab-org" and label = "group::code review"
  and label in ("backend", "cli", "frontend") and label != "type::ignore"
  and milestone = "18.3" and state = opened
  and assignee = none
Scheduled issues (sort by epic) backend 
display: table
fields: epic, title, assignee, weight, labels("type::*", "Deliverable", "Stretch")
query:
  group = "gitlab-org" and label = "group::code review"
  and label in ("backend", "cli") and label != "type::ignore"
  and milestone = "18.3" and state = opened
Scheduled issues (sort by epic) frontend 
display: table
fields: epic, title, assignee, weight, labels("type::*")
query:
  group = "gitlab-org" and label = "group::code review"
  and label in ("frontend") and label != "type::ignore"
  and milestone = "18.3" and state = opened

Slippage from 18.2

Open backend issues from 18.2 
display: table
fields: health, assignee, weight, labels("backend-weight::*", "workflow::*"), labels( "Deliverable", "Stretch"), title
query:
  group = "gitlab-org" and state = opened and milestone = "18.2"
  and assignee in ("garyh", "kinsingh", "marc_shaw", "patrickbajao", "dskim_gitlab")
Open frontend issues from 18.2 
display: table
fields: health, assignee, weight, labels("frontend-weight::*", "workflow::*"), labels( "Deliverable", "Stretch"), title
query:
  group = "gitlab-org" and state = opened and milestone = "18.2"
  and assignee in ("iamphill", "slashmanov", "thomasrandolph")

Candidate issues to consider

High priority

Saturation issues: GitLab.com Resource Saturation 
display: table
fields: labels("severity*"), labels("priority*"), title, epic, assignee, milestone
query:
  type in (Issue, Epic)
  and group = "gitlab-org" and label = "group::code review"
  and label = "GitLab.com Resource Saturation"
  and state = opened

Next 1-3 releases

Open backend issues from Next 1-3 releases 
display: table
fields: epic, title, assignee, weight, labels("backend-weight::*", "workflow::*")
query:
  group = "gitlab-org" and label = "group::code review"
  and label in ("backend") and label != "type::ignore"
  and milestone = "Next 1-3 releases" and state = opened
Open frontend issues from Next 1-3 releases 
display: table
fields: epic, title, assignee, weight, labels("frontend-weight::*", "workflow::*")
query:
  group = "gitlab-org" and label = "group::code review"
  and label in ("frontend") and label != "type::ignore"
  and milestone = "Next 1-3 releases" and state = opened

Quick wins

Weight 1 backend issues 
display: table
fields: assignee, weight, title, milestone, updatedAt
query: group = "gitlab-org" and label = "group::code review" and label = "backend" and weight = 1 and state = opened
Weight 1 cli issues 
display: table
fields: assignee, weight, title, milestone, updatedAt
query: project = "gitlab-org/cli" and label = "group::code review" and weight = 1 and state = opened
Weight 1 frontend issues 
display: table
fields: assignee, weight, title, milestone, updatedAt
query: group = "gitlab-org" and label = "group::code review" and label = "frontend" and weight = 1 and state = opened
quick win issues 
display: table
fields: assignee, weight, title, milestone, updatedAt
query: group = "gitlab-org" and label = "group::code review" and label = "quick win" and state = opened

Stable counterparts

Staff+ engineers

All engineers are welcome to contribute to the planning process! Staff+ engineers are expected to contribute, see references below, and are therefore tagged here explicitly to ensure visiblity as soon as the issue is created.

Handbook references:

  • Staff+ archetype - Tech Lead
    • "A Staff Engineer partners with the Engineering Manager and the Product Manager for milestone planning"
  • Staff+ archetype - Right hand
    • "Staff+ Engineers are supposed to broaden the perspectives of their managers. Decision-makers often need the additional context and perspective to make well-informed decisions about investments in the product architecture, understanding expected ROI"
  • Development Staff career framework
    • "Works with the Engineering Manager to assign work to the team"

Missing labels / weights

%18.3 issues without a backend / frontend / cli label (list should be empty except for documentation only issues):

display: table
fields: assignee, labels("documentation"), title
query:
  group = "gitlab-org" and label in ("group::code review") and milestone = "18.3"
  and label != "type::ignore" and state = opened
  and label != "frontend" and label != "backend" and label != "cli"

%18.3 issues without a weight (list should be empty):

display: table
fields: assignee, labels("backend", "frontend"), weight, labels("backend-weight::*", "frontend-weight::*"), title
query:
  group = "gitlab-org" and label in ("group::code review") and milestone = "18.3"
  and label != "type::ignore" and state = opened
  and weight = None

*-Abilities

Deliverable issues should be labelled with an Abilities::* label if they contribute to one of the *-abilities.

18.3 deliverables 
title: Deliverable issues
display: table
fields: epic, title, labels("backend", "cli", "frontend"), labels("type::*", "maintenance::*", "feature::*", "bug::*"), labels("Abilities::*")
query:
  group = "gitlab-org" and label = "group::code review"
  and label in ("backend", "cli", "frontend") and label != "type::ignore"
  and label = "Deliverable"
  and milestone = "18.3"

(improve this template?)

Edited by François Rosé