Code Review 17.7 Planning : November

Release planning for the Code Review Group

Overview - 17.7 Release Board

Backend

Planning distribution

• typefeature: w16 = 73% (excluded: +w3 Stretch)
• typemaintenance: w2 = 9% (excluded: +w1 Stretch)
• typebug: w4 = 18%

Priorities

0. Security
1. AI
   1. Duo Code Review external release &14825 (closed)
   2. 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.
2. Cells 1.0 - &12795 - @kerrizor will continue this for the moment.
3. Policy mergeability check - &13808 - rollout was reverted, need an issue to address the problem
4. Stacked Diffs for the CLI - &12025 - lot of internal enthusiasm, good to spend time on it
5. Patch ID - gitlab#450391 (closed)
6. Rapid Diffs - &13764 (closed) - André will ping Patrick next week to identify issues based on the MVC plan
7. Merge&rebase in 1 click - gitlab#895 - also fixes a Source Code issue
8. /remind_me - &13628 - parked

Frontend

Planning distribution

• typefeature:
• typemaintenance:
• typebug:

Priorities

1. MR Homepage - Testing/Responding to Feedback, buffer for critical fixes based on feedback
2. Rapid Diffs (++)
3. Reports Tab - &13808 -
4. Merge request listing page to Vue (&10827 (closed)): Buffer for potential bug reports

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.

• backend: @patrickbajao
• frontend: @iamphill

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.7 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.7" and label != "type::ignore" and opened = true and label != "frontend" and label != "backend"  and label != "cli"

%17.7 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.7" and label != "type::ignore" and opened = true and weight = None

(improve this template?)