Source Code group 12.3 planning (Sep 22)
Release planning for the Source Code group
12.3 Release Board
Overview –Slippage from 12.2:
- Move "Require code owner approval" setting from project interface to protected branches interface was split into two issues, API https://gitlab.com/gitlab-org/gitlab-ee/issues/10395 and interface https://gitlab.com/gitlab-org/gitlab-ee/issues/13251 – we need to complete the interface in 12.3
In 12.3, priorities are:
- Feature debt: approval rules
- Customer priority https://gitlab.com/gitlab-org/gitlab-ee/issues/1411
-
Product Vision FY20 ~"code review"
Continue laying the foundation for merge-ref powered merge request diffs https://gitlab.com/gitlab-org/gitlab-ce/issues/58245- Start tackling merge request performance through progressively loading diffs file by file https://gitlab.com/gitlab-org/gitlab-ce/issues/62536
- Product Management OKR
-
backend OKR
- TBD
-
frontend OKR
- TBD
UX
Please see UX board for full release plans
Frontend
Frontend 12.3: Deliverable / Stretch Board
Please see Frontend board for this release
- FE weight: TODO
Backend
Backend 12.3: Deliverable / Stretch Board
Please see Backend board for this release
- BE weight: 43
Product process checklist
Notes to self, and to help me document my process for new PM's as they join. I typically work through these boards and issues, in the order listed below grooming the issues.
Boards
- Create groups for milestone - make sure every issue in the milestone has the correct group assigned
- Deliverables / Stretch / NPR for milestone - quick view of what is/isn't deliverable, pretty much everything non-deliverable should be removed from the milestone by kick off to prevent confusion that it will be implemented
- BE / FE / Discovery for milestone - make sure very issue has either BE, or FE, or both assigned
- Create groups for HackerOne - make sure every HackerOne security issues has the correct group assigned
- Bugs
Lists
- Security issues sorted by due date - make sure all security issues with an upcoming due date are assigned to meet our security SLA
- Bugs
Checklist
-
Groom the issues already assigned to the current milestone for correct label hygiene -
Check/update past milestones for wayward issues -
Check/update relevant category visions (source code management, code review) -
Add vision items -
Add security items -
Add bugs -
Carefully check ~promised items for customers are scheduled or well communicated
Edited by James Ramsay (ex-GitLab)