Knowledge Group 12.4 Planning
Release planning for the Knowledge Group
12.4 Release Board
Overview -In 12.3 the team continued working on polish and bug fixes for Design Management. This included better support for design links across Gitlab, UI/UX improvements related to information and usability, and some bug fixes.
The team also worked on features to provide richer data to design thumbnails and began to lay the groundwork for creating various sized images for so that Designs can be leveraged with more optimized images across the rest of the GitLab issue and other places in the app.
Product and Design also began collaborating on discovery for Design Review and Approval workflows.
In 12.4 we're focusing on continuing to expand the available data for design management via resized images and additional API endpoints. These will further our ability to expose designs across various portions of the GitLab application.
We're also going to be tackling some work on Wiki's to improve the editing experience and refine a plan for Group Level Wikis.
Finally we'll need to address some bugs across Design Management in this release:
UX
Please see the UX Board for this release
Frontend
Frontend 12.4: Deliverable / Stretch Board
Please see the FE Board for this release
- FE Weight: TODO
Backend
Backend 12.4: Deliverable / Stretch Board
Please see the BE Board for this release
- BE Weight: TODO
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
- knowledge 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
- knowledge 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 (Design Management, Wiki) -
Add vision items -
Add security items -
Add bugs -
Carefully check ~promised items for customers are scheduled or well communicated