Skip to content

Code Review 17.9 Planning : January

Release planning for the Code Review Group

Overview - 17.9 Release Board

Backend

Planning distribution

Priorities

  1. Security - no open issues
  2. infradev
    1. Remove old commits - https://gitlab.com/groups/gitlab-org/-/epics/16385 - short runway, high complexity -> investigate
    2. Bigint migration - &13435 - long runway, low complexity -> no action for now
  3. corrective action &13512
    1. gitlab#510562 (closed) - fix merged MRs that were marked as closed -> figure out how many were impacted
    2. gitlab#506833 (closed) - investigate SLO violation
  4. MR download bug - https://gitlab.com/gitlab-org/gitlab/-/issues/511302
  5. AI
    1. Duo Code Review external Experiment - &14825 (closed)
    2. Duo Code Review Beta - &16298 (closed)
    3. GA other features - &10347 or &10769 - preference towards Code Review Summary. Could do FE changes from UX feedback. Capacity is the main thing holding us back.
  6. Cells 1.0 - &12795 - @kerrizor will continue this for the moment.
  7. Auto-merge bugs - &16143
  8. Feature flag cleanup - gitlab#502721 (closed) - document process change to keep this in check
  9. Stacked Diffs for the CLI - &12025 - pause, get feedback
  10. Rapid Diffs - &13764 (closed) - pause in favor of infradev?

Frontend

Planning distribution

Priorities

  1. MR Homepage - Implementing the new UI proposal
  2. Reports Tab - &13808 - use
  3. Duo Code Review - self managed (issue TBC)
  4. Rapid Diffs (++)
  5. Feature Flags cleanup - focus on devising a process change.

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

%17.9 issues without a backend / frontend / cli label (list should be empty):

---
display: table
fields: assignee, weight, title
---
group = "gitlab-org" and label in ("group::code review") and milestone = "17.9" and label != "type::ignore" and opened = true and label != "frontend" and label != "backend"  and label != "cli"

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

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

(improve this template?)

Edited by François Rosé