Source Code Planning 15.1
Release planning for the Source Code Group
Overview
Build Boards
Key Themes
Category | Theme | Why | Workflow |
---|---|---|---|
Feature |
Implement gitlab-sshd on GitLab SaaS & Applying GitLab SaaS IP Allowlisting for SSH |
IP allow listing for SSH | in development |
Bugs | Security / Availability | reduce risk | in development |
Availability | Understand why we missed the target for the error budget | reduce risk | in analysis |
Feature | Win government deals | ||
Feature | Highlight source code syntax on the frontend using HighlightJS | Significant performance improvement when rendering large files | in development |
Feature | Source code rules - MVC | Improve user experience by making it easier to find and understand the complete set of different rules applied to each branch | starting development |
Documentation | Document how repository storage is calculated | Transparency |
in documentation with dev support |
Documentation | Improve documentation of merge options | Transparency |
in documentation |
Team Capacity
- Total Weight Capacity: TODO
- FE Weight: 9
- BE Weight: 10+6 (excluding capacity for work on IP allowlisting for SSH)
Planning Board
Planning -Product manager prepares the planning with proposed issues for the milestone. Engineering reviews and make recommendations based engineering allocation and capacity.
Checklist
Frontend Engineering Manager
-
Get Team Capacities and post them in a comment no later than the 10th of the month (@sean_carroll) -
Obtain weights for proposed issues -
Recommend issues via engineering allocation as applicable -
Assign Deliverable Items for Milestone
Backend Engineering Manager
-
Get Team Capacities and post them in a comment no later than the 10th of the month (@andr3) -
Obtain weights for proposed issues -
Recommend issues via engineering allocation as applicable -
Assign Deliverable Items for Milestone
Product Manager
-
Define Key Themes -
Prepare planning board and submit it for initial capacity assessment and review -
Signs off on final plan
Stable counterparts
-
Technical Writing (@aqualls)